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.

Operations:

• Project 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:

• Creating a component

Work Management

Sprint

A sprint, also known as an iteration, is a short period of time during which the development team implements and delivers a discrete and potentially shippable application increment. The deliverable can be a working milestone version. A typical sprint is two weeks. It's long enough to get something accomplished, but not so long that the team is not getting regular feedback. Sprint-based work organization is fundamentally different than Kanban, where the results are delivered continuously. In JIRA, sprints can be viewed on a board.

Kanban

Kanban is based on continuous delivery of work. Rather than planning iterations, the flow of work is constantly monitored to endure that there are always tasks being worked on. When the tasks are completed, new tasks are pulled into work-in-progress.

TODO: https://confluence.atlassian.com/jirasoftwarecloud/monitoring-work-in-a-kanban-project-764478148.html

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.

Bug

A bug is a problem which impairs or prevents the functions of the product.

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

Fields Reference

updated, updatedDate

updated

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

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.

https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-764478330.html

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:

• Issues Worked on Since Yesterday Midnight

JQL

Functions

Functions Reference

Time Functions

Also see Time Format.