JIRA

JIRA:

- It is defect tracking, project management tool by Atlassian Inc.

- Current version is 6.

- It is platform independent.

Who uses JIRA?

- Software project development teams, help desk systems, leave request systems etc.

- for QA it is used for:

- bug tracking

- tracking project level issues

- tracking environmental issues.

Basics of JIRA:

- Based on 3 concepts:

- Issue : Every task, enhancement request; basically anything to be created and tracked via JIRA is considered issue.

- Project: collection of issues.

- Workflow: simply series of steps an issue goes through starting from creation to completion

Issue workflow:

- created/open

- work in progress

- completed/closed

Dashboard in JIRA :

Once logged in, dashboard page is displayed to user.

Dashboard gives snapshot about description of project you belong to;

issue summary and activity stream(issues that are assigned to you, issues that you created etc).

When you are trying to create/modify certain isssue under a project for first time, it helps to know about project itself.

- Go to main menu and choosing Project name from Projects drop down.

Projects:

Every project has following main attributes:

name- selected by administrator.

key: identifier that all issue names under project are going to start with.

- components:

- versions

Below is how project details are displayed in JIRA:

Please note left hand side navigation

- when i choose components option, it displays two components in project.

- when i choose versions option, versions within project are displayed.

- when i choose roadmap, version information is displayed with dates giving general idea about

important milestones in project.

- when i choose calendar option, we can view milestones date wise.

Creating an JIRA issue:

- click on create issue button.

Project:

- Every issue belongs to project.

- choose same by clicking on drop down and choosing project you want this issue to belong to.

Issue type: Bug, New Feature, Task, Improvement, Epic, Story.

Epic and story belong to agile projects.

Epic is group of stories.

Story is requirement in Agile that needs to be tracked from start to finish.

Summary:

Give your bug a title here.

There should be an option to clear contents on the screen.

Priority:Critical, Blocker, Major, Minor, Trivial.

Component: display components of Project

Affecter version and fix version:

will display versions available for project.

Assignee: name of person to whom this issue should be handed over further.

Can also assign issue to yourself.

Description: optional to enter as much info as you like about your issue.

Ex of description:

- choose state as california and click on city drop down- all states are displayed and user can select city

as needed.

- choose state as lousiana and click on city drop down- list is empty

- cities are empty for states New jersey and utah also.

provide exact steps, exact data and any other information you think necessary to complete this field.

Attachment:

supporting document can be uploaded with  an issue.

Test for subtask creation:

- open issue. go to more drop down in option on top. choose create subtask option from list.

Converting an issue to subtask:

- Go to more drop down list and choose Convert to Subtask option.

Important points:

- you can have as many subtasks as needed under the issue

- once you create subtask under parent, parent can no longer be converted to subtask.

- subtask can be converted to parent issue. more>convert to issue option.

Managing issues with JIRA:

- Edit:

- Comment:

- Assign:

- More:

- Log work:

- Move issues

- Link:

- Clone:

- Email:

- Export: