Embed Size (px)
Citation preview
OHM Training 2016
JIRA / Servicedesk
OHM Training 2016
Jira / Servicedesk Introduction In Ohm all program errors must be reported via Jira / Servicedesk. Jira/servicedesk is a bug tracking tool. This tool aims to: - Follow up the full life cycle of bugs.
• Errors reported via phone or e-mail risk to sink to the bottom of the programmers priorities.
Jira adds the error to the to-do list that is used by the programmers to organize their job.
• Jira saves the bug and periodically reminds the programmer to take action.
• Jira will automatically send feedback to the bug-reporter whenever the status of a bug changes.
• Jira errors are included in the acceptance tests for new releases.
- Automatically assign the bug to the correct person • People often have their known contact persons in the IT
department - Help in investigating the system.
• Analysis of the bugs reveals which parts of the system have the highest priority for maintenance and optimization.
OHM Training 2016
Log in to the Jira servicedesk: https://jira.ravago.com/servicedesk When you open the webbrowser you will get following startscreen
JIRA / Servicedesk
OHM Training 2016
You see the different domains that are accessible. If you want to enter the detailed menu, click on the domain you need.
JIRA / Servicedesk
OHM Training 2016
In the domains Gauss / JDE / OHM you can enter a bug or ask for support. You can see it on the left side of the page. Gauss / JDE OHM Bugs => When you need to report a real bug. Support => When you need something to be changed (the RFS that
we used in Bugzilla)
JIRA / Servicedesk
OHM Training 2016
Following domains are accessible in Jira 1/
JIRA / Servicedesk
OHM Training 2016
1/ GAUSS (Datawarehouse) Bugs Support
JIRA / Servicedesk
OHM Training 2016
When you select a domain in Gauss, you will be redirected to the detail page:
JIRA / Servicedesk
OHM Training 2016
Enter a short description in the Summary box The priority is default on Major (P3) but is changeable The environment is default on None, you need to select the correct one
JIRA / Servicedesk
OHM Training 2016
Enter a detailed description in the description box The Project is default on Application Maintenance, but changeable You also can add an attachment Save your bug
JIRA / Servicedesk
OHM Training 2016
You get an overview of your entered bug with reference, type and status
JIRA / Servicedesk
OHM Training 2016
2/
JIRA / Servicedesk
OHM Training 2016
JIRA / Servicedesk
OHM Training 2016
JIRA / Servicedesk
When you select one of these domains, you will be redirected to the following detailed page
OHM Training 2016
Enter a short description in the summary box The priority is default on Major (P3) but is changeable Select your location
JIRA / Servicedesk
OHM Training 2016
Enter the detailed description in the description box You also can add an attachment Save your bug You see the overview of your bug, with status, reference and type
JIRA / Servicedesk
OHM Training 2016
3/ Bugs Support
JIRA / Servicedesk
OHM Training 2016
When you want to enter a bug in this domain, you will be redirected to following detail screen
JIRA / Servicedesk
OHM Training 2016
Enter a short description in the summary box The priority is default on Major (P3) but is changeable Enter a detailed description in the description box The Project is default on Application Maintenance, but changeable
JIRA / Servicedesk
OHM Training 2016
You see the overview of your bug, with status, reference and type
JIRA / Servicedesk
OHM Training 2016
4/ Bugs
JIRA / Servicedesk
OHM Training 2016
Wen you want to register a bug for Ohm you will see following detail page
JIRA / Servicedesk
OHM Training 2016
The difference with the other domains is that when you want to register a bug for Ohm, all the fields are mandatory The priority is default on Major (P3) but is changeable
JIRA / Servicedesk
OHM Training 2016
The environment is default on None, you need to select the correct one There are only 2 environments that you can select. When you have an issue in Fatman / GEM / ... Reproduce the problem in Reshot and register a bug under OHM Reshot
JIRA / Servicedesk
OHM Training 2016
Project is default on Application Maintenance, but changeable You also can add an attachment Save your bug
JIRA / Servicedesk
OHM Training 2016
You see the overview of your bug, with status, reference and type When you register a bug in the domain OHM, the first status of your bug will be PENDING APPROVAL. The responible process owner needs to approve this.
JIRA / Servicedesk
OHM Training 2016
Helpdesksupport: Support You can use this if you don’t know to which domain you have to link your problem.
JIRA / Servicedesk
OHM Training 2016
When you click on create your bug will be opened.
JIRA / Servicedesk
OHM Training 2016
HELP ME
JIRA / Servicedesk
OHM Training 2016
JIRA / Servicedesk Choose the Component that closely resembles the domain in which the change should be applied. The environment is default on None, you need to select the correct one There are only 2 environments that you can select. When you have an issue in Fatman / GEM / ... Reproduce the problem in Reshot and register a bug under OHM Reshot
OHM Training 2016
JIRA / Servicedesk
Project is default on Application Maintenance, but changeable Save your bug
OHM Training 2016
You see the overview of your bug, with status, reference and type
JIRA / Servicedesk
OHM Training 2016
5/
JIRA / Servicedesk
OHM Training 2016
These are the “domains” you can access via Jira. When you select a certain domain you can see in the header of the page in which domain you are currently working. You can also navigate quickly to the start screen of the Service Desk in this section. (just bove the domain name) You can also see an overview of all your requests by clicking on My request You will see all your requests
JIRA / Servicedesk
OHM Training 2016
In this part of Jira, you can change some data so you can search on issues / bugs. I can specify if I want to see All requests / Open requests /Closed requests / Custom filter f.e. All Requests
JIRA / Servicedesk
OHM Training 2016
Different statusses of a BUG. 1/ Pending Approval (processowner needs to approve the bug) 2/ Open (when processowner accepted the bug) 3/ In progress (when developer opens the progress) 4/ Fixed (when developer fixed the progress) 5/ Deployed – In test (when release manager deployed the solution) 6/ Tested (when you and it is ok) Reopened (when you tested and not ok) 7/ Verified (when processowner verified the bug) 8/ Closed (when release manager closed the bug)
JIRA / Servicedesk
OHM Training 2016
END
Contact details
Chris VAN DOORSLAER
( +32 14 701 775
Fax +32 14 701 596 +32 490 588 276 Skype chrisvandoorslaer
