Jira is a proprietary issue tracking product, developed by Atlassian. It provides bug tracking, issue tracking, and project management functions. It is used by over 25,000 customers in 122 countries around the globe. JIRA Workflow is one of the administrative utility for JIRA administrators for managing their task hierarchy.
This blog is to specifically help JIRA based organisations to manage their workflow mechanism to achieve a matured and structured project tracking and management system.
NOTE: If you are reading this blog, then it is assumed that you have knowledge about what JIRA does and why it is used. The context is to help the software development and quality analyst (QA) teams to start functioning on the core system rather than drawing their workflow which is sought of standardised across the companies.
| From | Transition | To | |
|---|---|---|---|
|
Complete Requirements
|
→ | ||
|
Close Issue
|
→ | ||
|
Start Progress
|
→ | ||
|
Missing Tech Requirements
|
→ | ||
|
Close Issue
|
→ | ||
|
Development is Complete
|
→ | ||
|
Task Completed
|
→ | ||
|
Freeze Issue
|
→ | ||
|
Code Review is In Progress
|
→ | ||
|
For Testing
|
→ | ||
|
In Testing
|
→ | ||
|
Disabled Feature
|
→ | ||
|
Encountered Bugs / Errors
|
→ | ||
|
No Bugs / Errors
|
→ | ||
|
Start Progress
|
→ | ||
|
Deployed to Production
|
→ | ||
|
Verified to Production
|
→ | ||
|
Reopen Issue
|
→ | ||
|
Reopen Issue
|
→ | ||
|
Close Issue
|
→ | ||
|
Reopen Issue
|
→ | ||
|
Close Issue
|
→ | ||
|
Start Progress
|
→ | ||
| There are no transitions out of this status | |||
|
Completed Tech Requirements
|
→ | ||
|
Unfreeze Issue
|
→ | ||
Importing workflow into JIRA
Conclusion
An industry acceptable JIRA workflow is ready for your team to work with a standard process.
It’s not possible to directly import workflows in the Atlassian Cloud environment.
https://confluence.atlassian.com/jirakb/how-to-import-a-workflow-into-a-jira-cloud-application-779160755.html
Yes, correct!
Abhilash, thanks for the QA workflow. I have a few questions. There is a transition from In Progress to Done. Normal software development should not take this route, ie no work is tracked. Can you explain the purpose of this transition? Also there is a transition from Released to Closed. What event should trigger this if verification occurs before Released. Lastly, what issue types should this apply to?
Dear Mike, thanks for your question. Primarily, the transition from Progress to Done signifies “Feature Drop” wherein while the feature is under development and because of any unforeseen circumstances the feature gets dropped in between, tracking the same and keeping in its history marked.
Secondly, the idea of realized to emphasize the complete development to the stage and to final production deployment. “Released” defines that the feature has successfully deployed to either stage or production server. Every ticket has to be closed to avoid followups. Though this evolves as per the team’s internal requirement changes.
Can you suggest me about setup each status into columns.
Which column do we have in board if we follow this workflow?
Thank you.
How can I import this workflow to Jira Cloud?
It is currently not possible to directly import a workflow due to it being one of the Functional differences in Jira Cloud products.
How is your board configured? To many columns if one per state