JIRA Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 6: Line 6:


* Administering a Project https://confluence.atlassian.com/jiracorecloud/administering-a-project-765593096.html
* Administering a Project https://confluence.atlassian.com/jiracorecloud/administering-a-project-765593096.html
A ''project'' is a collection of [[#Issue|issues]].


==Component==
==Component==

Revision as of 22:42, 27 February 2016

Internal

Project

A project is a collection of issues.

Component

A component is a way to group issues within a project. Components do not have dates assigned to them. They can can have a component lead who could be a subject matter expert.

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

Task

Bug

Story

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