JIRA Concepts

From NovaOrdis Knowledge Base
Revision as of 23:02, 27 February 2016 by Ovidiu (talk | contribs) (→‎Component)
Jump to navigation Jump to search

Internal

Project

A project is a collection of issues.

Component

A component is a way to group issues within a project. They can be seen as sub-sections of the project. They are used to group project's issues into smaller, more manageable groups.

Components do not have dates assigned to them.

Components can have a component lead who could be a subject matter expert. Once an assignee is set for a component, it will override the project's default assignee for issues that are created within that component.

Operations:

Issue

An issue is a unit of work that need to be done. The issue is the building block of any project.

An issue can have sub-tasks that can be assigned and tracked individually.

Operations:

Types

Story

A story is a software system requirement that is expressed in a few short sentences, ideally using non-technical language. In JIRA Agile, a story is represented as an issue, and individual tasks within the story are represented as #Sub-Task#sub-tasks.

Task

A task is a unit of work contained within a story. In JIRA Agile, individual tasks are represented as sub-task issues, and stories are represented as parent issues.

Bug

Epic

Sub-Task

A sub-task can be created for an issue to either split the issue into smaller chunks, or to allow various aspects of an issue to be assigned to different people.

Once broken down into sub-tasks, an issue cannot be resolved until all its sub-tasks are resolved.

However, if it is becoming obvious that a sub-task is holding up the resolution of an issue, that sub-task can be converted to an issue, which can be worked on independently of the original parent issue. The reverse is also true: if it is becoming obvious that an issue is really just a sub-task of a bigger issue, the issue can be converted into a sub-task of that issue.

Sprint

A sprint (or an iteration) is a short period in which the development team implements and delivers a discrete product increment, e.g. a working milestone version. Sprints are ideally two to four week long.

Backlog

The backlog is where sprints are planned.