JIRA Concepts
Internal
Project
- Administering a Project https://confluence.atlassian.com/jiracorecloud/administering-a-project-765593096.html
A project is a collection of issues.
Operations:
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. 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
- 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:
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.
Bug
A bug is a problem which impairs or prevents the functions of the product.
Epic
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.
Fields
asignee
updated, updatedDate
You need to be careful when using 'updated' in queries, as its semantics is actually "last update timestamp". If the issue was updated multiple times, only the last update timestamp is retained and counts in the query.
timeSpent
Time Format
Also see Time Functions.
Absolute Time Format
'yyyy/MM/dd HH:mm' 'yyyy-MM-dd HH:mm' 'yyyy/MM/dd' 'yyyy-MM-dd'
Period Format
10m 10h -5d 2w 2d
Sprint
- JIRA glossary - Sprint: https://confluence.atlassian.com/agile/glossary/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
- Using the backlog https://confluence.atlassian.com/agile/jira-agile-user-s-guide/using-a-board/using-the-backlog
The backlog is where sprints are planned.
Filter
Filter, named filter, custom filter.
Custom Filters
Filters can be named and saved. To access saved filters: Diamond -> Issues and filters -> View all filters -> Filter by Owner dropdown box.
Examples of custom filters:
JQL
Functions
Time Functions
Also see Time Format.