JIRA Tutorial: A Complete Guide for Beginners: BUG MANAGEMENT TOOL

INTRODUCTION

Jira is a Project Management tool which is basically used to track bugs. Using Jira one can

Capture, track, and resolve bugs throughout the entire development process.

BUG LIFE CYCLE

It is a journey of a defect (bug) cycle, i.e. It starts when we found a defect and it ends when it is closed.

Flow of Bug Life cycle:

as “New” and then “assign” the same to the respective developer.

Now the developer will change the state of the ticket to “Open” to work on it but he

need to make sure whether the ticket is “Duplicate” or “Deferred” or “Rejected”

or “Not a bug”.

Once the ticket is “fixed” then the developer will assign it back to the reporter.
Now the reporter will verify the bug (retest)

If it is reproducible then will reopen the ticket and will assign it back to the developer.
If it is not reproducible then he will verify and close the ticket.

JIRA DASHBOARD

One can use the Jira trial free version and create his own project (Ex: Testing Jira) using his account

STEPS TO CREATE A PROJECT IN JIRA

Click on the “+” button from the left-Hand side panel and click on Projects option.

Already added projects will display on the page.

2. Click on Create Projects button on the right top corner and you will get redirected to Create project page.

3. Click on Change template button if you want to select a specific template for the project i.e Scrum, Kanban etc.

4. Enter project name on Create project page and click on Create button to create a project.

Once the project is created, you will navigate to the dashboard.

STEPS TO CREATE A BUG

1. Click on the “+” button from the left-Hand side panel.

2. Make sure that the following fields are filled up:

Project should be selected as “Testing Jira” and Issue Type as “Bug” by default.
Summarize the bug in a single line.
Add a description for it which should include the following points:

Add a label to distinguish the bug (Ex: manual or automation)
Enter the list of devices on which this issue is reproducible and the browser on which you reproduced. For ex,

for this issue. It can be a screenshot or a video.

Now suppose this issue is blocked, cloned or related (category) to any previous issue reported then you can select that category under “Linked issues” dropdown and enter its corresponding ticket under “Issue”.

Select the scrum master (who manages the process in Agile) or the developer who is going to work on this ticket as an Assignee.

Enter an Epic link (used to differentiate among functionalities inside a project) for the same.
Select the sprint in which this bug is created.

Now click on “create” button to create the bug. The assignee will receive an email notification for the same.

STEPS TO TRACK A BUG

Once the bug is created and assigned to the respective developer, then the developer will be able to view that bug by clicking on “My open issues” filter.

Once the developer starts working on it then he/she needs to update the ticket by changing the state of the ticket to “In Progress”.

If it is not fixed (still reproducible) then assign the ticket back to the developer with proper reproducible steps and attached video or screenshot and also change the status to “In progress”.