Jira tutorial view issue
In this Jira tutorial view issue, we will learn how to view an existing issue and how we can edit a previously created issue. If you have do not know how to create an issue click here.
Step 1 Image 1: Click Issue icon
Click the issues link on main screen, and select the recent issue.
Step 2 Image 2: View Issue screen
The issue screen has several important icons on top. Here we have Edit, comment, assign, backlog, selected for development, workflow and admin.
Step 3 Image 1: Workflow
- The next icon is view workflow.
- Here you can see this ticket’s assigned workflow.
Step 3 Image 2:
- Workflows keep track of unique points in the process that you are trying to monitor.
- JIRA offers different workflows. It also provides administrators the ability to configure and build new workflows from scratch.
Step 4 Image 1: State transitions
- The next item is transitions. These transitions are also customizable.
- Click on in progress transition icon.
- There will be a small change in status. This means you have transitioned this issue into its next status.
- Status and transition names do not have to match. Sometimes if you click a transition, example begin work you might end up observing your ticket enter the in progress status
Step 4 Image 2: Change in status observed below after clicking in progress.
Step 4 Image 3: Change priority
- The next item on the list is priority
- You can change the tickets priority based on the urgency
- This item is also cuztomizable by the administrator
Step 5 Image 1: Edit button
Pressing the Edit button will bring up the edit screen.
Step 5 Image 2 : Edit screen
Here you can make the necessary changes to an existing issue. Shown below are the fields that you can edit.
Step 6 Image 1 : Comment button
Used to add additional details about the issue.
Issue 6 Image 2 : Add comment screen
Step 7 Image 1: Assign button
Assign button that will bring up a popup to choose a new assignee who is going to work on the issue.
Step 7 Image 2: Add assignee screen
- Select the assignee and add comments
- Click assign and the new assignee gets this issue assigned to him or her.
Step 8 Image 1 : Share button
On the far right, we have a Share button that allows you to email a link to that issue to whomever you choose, but they will not be able to view it if they do not have access to the project or the instance.
Step 9 Image 1: Export button
The next button, Export, allows you to export the issue itself as a file, in a Word or XML file or it also allows you to print out the issue.
Step 10 Image 1: More button
The last button is the “More” button. This button contains many options like log time, Agile board, rankings, attach files, watchers etc.
Step 10 Image 2: Log work
Selecting more button and then choose Log Work. This allows you to place an estimate on how much time it took you to finish the ticket. The option turned on or off based on the project situation and the role of the user.
Step 10 Image 3: Agile ranking
The next three options are for Agile ranking of issues. If you have a Scrum master who triages your tickets, they can place it on the board and they can set a rank, higher or lower than it currently exists.
Step 10 Image 4: Attach files
The next option is Attach Files, which allows you to attach a file to the actual issue itself. “Voters” is a completely optional field that allows you to vote on issues such as feature requests if your company provides you the option to do so.
Step 10 Image 5 : Watchers
The next option is Stop Watching because as the creator, you are an automatic watcher of the issue. As a watcher, you will receive email notifications whenever this issue gets modified.
You can go to any issue that you have access to and if you are not already a watcher, you can start watching that issue, at which point you will receive email notifications even if you are not directly tied to that specific issue so you can easily monitor its progress. I can select Watchers to see who else is watching the issue. As you can see right now, it is only me. I can also add other watchers myself in that screen. Next up, we will be going over sub tasks and other additional features.