JIRA Concepts

Internal

• JIRA

Project

• Administering a Project https://confluence.atlassian.com/jiracorecloud/administering-a-project-765593096.html

A project is a collection of issues.

Component

• Organizing work with components https://confluence.atlassian.com/jiracorecloud/organizing-work-with-components-765593655.html

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

• Working with issues https://confluence.atlassian.com/jiracorecloud/working-with-issues-765593800.html
• Creating issues and sub-tasks https://confluence.atlassian.com/jiracorecloud/creating-issues-and-sub-tasks-765593815.html
• Customizing the issues in a project https://confluence.atlassian.com/jiracorecloud/customizing-the-issues-in-a-project-765593617.html

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:

• Configure an Issue's Fields

Types

Story

• JIRA glossary - Story: https://confluence.atlassian.com/agile/glossary/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

• JIRA glossary - Task: https://confluence.atlassian.com/agile/glossary/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.

Sub-Task

• Creating a sub-task https://confluence.atlassian.com/jiracorecloud/creating-issues-and-sub-tasks-765593815.html#Creatingissuesandsub-tasks-CreateSubtaskCreatingasub-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

• JIRA glossary - Sprint: https://confluence.atlassian.com/agile/glossary/sprint

Backlog

• Using the backlog https://confluence.atlassian.com/agile/jira-agile-user-s-guide/using-a-board/using-the-backlog