Atlassian Jira

JIRA is a tool developed by Australian Company Atlassian. It is used for bug tracking, issue tracking, and project management. The name "JIRA" is actually inherited from the Japanese word "Gojira" which means "Godzilla".1



A Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle, and typically represents a process within your organization.2

Statuses and transitions

A status represents the state of an issue at a specific point in your workflow. When defining a status, you can optionally specify properties.3

To Do Work that has not been startedUser Stories with Acceptance Criteria
In ProgressWork that is actively being looked at by the teamDevelopment with Unit Testing and Automated Acceptance Testing (Robot Framework); Create a Pull Request for Peer Code Review
Code ReviewWork that is completed, but awaiting reviewPeer Code Review and Functional Testing
Ready to MergeCode that has been reviewed and is ready to merge into the master or release branch
IntegrationIntegrate/Merge code into the Master branch and verify using Automated Acceptance Testing then deploy to the Beta environmentMerge into Master, Robot Framework, Continuous Delivery (Beta)
Awaiting UATWaiting for User Acceptance TestingThe application has been deployed to a Beta/Staging environment
User Acceptance TestingClient and Product Owner perform User Acceptance TestingUAT is also known as beta testing, application testing or end-user testing
Ready for DeploymentReady for deployment to the production environmentContinuous Delivery (Production)
DoneWork that is completely finished and meets the team's definition of doneThe application has been deployed to a Production environment

A transition is a link between two statuses that enables an issue to move from one status to another. In order for an issue to move between two statuses, a transition must exist.4



Last edited by MichaelAlber .
Page last modified on Tuesday April 7, 2020 22:17:20 UTC.