Curious to learn about working with issues using Jira? Then you’ve come to the right place.
The inception of Jira Software in 2002 gave organizations access to Jira project management tools that streamline the planning and execution processes for project management teams.
These software development tools compile all the project information in one place, allowing for the tracking of progress, measuring productivity, and the overall success of deliverables.
In this Jira tutorial for beginners, we give you a step-by-step guide on how to work with issues in Jira.
Step 1: Creating an Issue
Issues are the foundation of any Jira project, and they refer to any work that requires completion. A Jira issue is customizable; it represents a project task, all the user stories, software bugs, and other major features. Issues help to manage and estimate workload, all while keeping track of the team’s progress.
There are three ways to create an issue:
- Click the ‘Create’ button on the navigation bar at the top of the screen
- Select ‘Create Issue’ on the backlog (toward the bottom)
- Hit the plus sign on your board (only for projects that are team-managed)
Step 2: Creating a Sub Task
Although this is optional, sub tasks allow you to assign and track issues on an individual basis.
Here are some reasons for creating sub tasks:
- To divide an issue into smaller tasks
- To allow for the assignment of issues to individuals
- To generate a to-do list for an issue
To create the sub task, select the particular issue, then the ellipses (•••), and finally, ‘Create Sub-task’. Outline all the details to your preference, then click ‘Create’.
Step 3: Setting Issue Estimates
In Scrum, estimating issues means predicting how long certain aspects of the backlog take before completion.
The intent is to measure and achieve reliable velocity. This metric allows the teams to become consistent with their deliverables over each sprint.
To set an estimate, select the Jira issue and enter an estimation value at the ‘Estimate’ tab. Be sure to change this value before the start of a sprint. Otherwise, it shows up as a scope change on the burndown chart (a method of monitoring sprints and epics).
Step 4: Prioritizing the Issues
In order to give the team an idea of their work in progress, you have the option to rank issues in order of priority. This is possible for both Scrum and Kanban projects.
To rank your issues, go to the backlog or board, then click-and-drag the issues to arrange them in the order you see fit.
Take note that making these changes requires a default permission scheme. The first is ‘Schedule Issue’, and the second is ‘Edit Issue’.
Step 5: Flagging Issues
You have the option to flag issues, and this means pointing out specific issues for any reason you deem necessary.
It is a useful feature because it fosters collaboration and encourages communication among team members because they indicate that someone needs help or a problem needs solving. In any case, you can add a comment to outline or explain what the flag represents.
To add a flag, go to your board, then right-click on the issue and select ‘Add Flag’. The flag appears as a small orange icon on the bottom left of the issue.
Step 6: Transitioning Issues
When you transition issues, it demonstrates that the workflow is progressing.
A workflow comprises statuses and transitions. While statuses detail the state of a task (for example, whether it is in progress or resolved), transitions describe how the work status changes or moves.
Take note that the workflow of the project determines whether or not you are able to transition an issue. Jira provides built-in workflows which give you the option to either incorporate them into your project as is or make modifications according to your preferences.
To transition issues, click and drag the issues from one column to another.
Step 7: Filtering Issues
Issue filters allow you to categorize issues by hiding the ones you don’t want to see and focusing on the ones that you do.
Jira offers quick filters that you can use as is, but you also have the option to customize them. Here’s how to access the filter feature:
The Search Bar: Use this to only show issues that have certain search terms.
Quick Filters Menu: Here, you can access any quick filters you create. You also have the default template options to display issues according to recent updates or whether they are your assignments.
Assignee Menu: Use this menu to view issues assigned to any team member you select.
To customize your own quick filters on Scrum and Kanban boards, first, go to the board and click the ellipses (top right hand corner). Next, select ‘Board Settings’, and then the quick filters tab. Enter all necessary information, such as a name or a description, and click ‘Add’.
Step 8: Using Automation
Having a good handle on workflow is essential to the success of any project. Jira automation makes it so that you can remain up to date, manage multiple tasks, and save time during the Jira workflow.
Jira offers several options that allow you to automate any project in progress. Some of the most popular templates include:
Smart Auto-Assign: Automatic assignment of issues according to skill set, workload, or any other reason you prefer.
Auto-Create a Sub Task: After you create a Jira issue, make creating sub tasks automatic by populating certain fields.
Clone Issues: Duplicates an issue after it transitions.
Change Due Date: Automatic updating of an issue due date when it transitions to ‘In Progress’ status.
Jira Issues Tutorial: Key Takeaways
Jira, being a play on the Japanese word for ‘Godzilla’, functions just as the name suggests. It is a colossal project management and project tracking software. The free Jira dashboard is the focal point of this Jira tutorial, as you can access every function, from how to create issues and incorporate other Jira methods such as issue tracking and issue transitions.
Creating issues by using the default issue type scheme, adding a sub task, prioritizing, and managing workflow transitions are all useful features of this Jira project management tool that, in the end, lead to the success of the Jira agile project.