Jira Bug tracking tool tutorial : Atlassian Documentation

Jira Bug tracking tool tutorial : Atlassian Documentation

Before jumping to this tutorial : Go through our another article on Writing Efficient Test Cases

 

Jira : The basic use of jira tool is to track the issue and to track bugs related to software and mobile application. and  user for Project management. Jira is complete solution for project management provided by atlassianConfluence is the one place for all the team work, Create , Organize and discuss work with your team.

Jira work flow: Configuring Workflow

Jira provides a default workflow which looks like below

 

jira-defaultworkflow

jira-defaultworkflow

 

  1. JIRAOpen.
  2. Assign.
  3. Resolved.
  4. Reopen.
  5. Closed.
  1. Open: Test Engineer test the application according to the requirement, while testing if test engineer find any issues, test engineer can raise the issue and change the status as open.
  2. Assign: Test Engineer assign a issue to the developer present in the company to fix the issue and change the status as Assign.
  3. Resolved: Developer can check the issue and fix the issue occurred in the application or software and change the status as resolved.
  4. Reopen: Test Engineer retest the application to check whether the issue is really fixed by developer or not and if issue is not fixed test engineer can change the status as reopen.
  5. Closed: Test Engineer retest the software or application to check the issue was fixed by developer or not and if issue was fixed change the status as closed.

How to report bug in Jira tool

  1. Project: In project drop down select a project which we have to test.
  2. Issue type:

4

  • Task
  • Bug
  • Epic
  • Story
  • Task: Task that needs to be done.
  • Bug: A problem which impairs or prevents the functions of the product.
  • Epic: An Epic captures a large body of work. It is essentially a larger user story that can be broken down into a number of smaller stories.
  • Story: Story is user requirement.

5

  1. Summary: In summary field enter the brief description about the issue or bug.
  2. Reporter: Reporter is a test engineer or a person who is analyzing, finding and reporting a bug or issue.
  3. Components: Components are sub-sections of a project. They are used to group issues within a project into smaller parts. Application contains several components like for example take gmail application,which contain login component and compose component. if user mention particular component where the issue is occurred,its easy to find issue.
  4. Description: Description contains steps to reproduce an issue or bug. And steps of scenario.

 Example: steps to validate login button.

  1. Enter Username.
  2. Enter Password.
  3. Click on Login button
  4. Fix/Versions: 
  1. Priority levels in Jira:

7

  • Highest: This problem will block progress.
  • High: Serious problem that could block progress.
  • Medium: Has the potential to affect progress.
  • Low: Minor problem or easily worked around.
  • Lowest: Trivial problem with little or no impact on progress.

8

  1. Labels:
  2. Attachments:  An attachment is any file that is included with your page. Examples of attachments are screenshots, photographs, other images, Word documents, presentations, PDF documents.
  3. Linked Issues:
  4. Issue: Select issue type, issue is either functional or integration or UI issue (User Interface).
  5. Assignee: Assignee is a developer or person who is fixing a issue.
  6. Epic Link: 
  7. Sprint: Time taken to complete a project is called as sprint.

 Posted By

Vinayak Mudiyappanavar,

Trainee Test Engineer