The Jira How-To Guide
•
1 like•320 views
This is a guide for product issues management and development process using Jira. The Issue Types and Workflows can be customized by Jira system administrators. Every development team should always discuss and define its own standards to follow. This slide shows the common Issue Types and Workflows for your reference, and some brief views of the Scrum Board and Reports.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to The Jira How-To Guide
Similar to The Jira How-To Guide (20)
More from Wilson Su
More from Wilson Su (13)
Recently uploaded
Recently uploaded (20)
The Jira How-To Guide
- 1. The Jira How-To Guide Wilson Su
- 2. Agenda 2 Workflows2 Scrum Board & Reports3 Good Practice4 Issue Types1
- 4. Issue Types Epic Story Task Sub-task BugDesign Requirement Improvement Task Note: Task includes, but not limited to, Research, Discussion, Development, Testing, and Debugging. 4
- 5. 5 Workflows
- 6. OPEN IN PROGRESS CLOSED Create RD Start Complete A Simple Workflow Example Transition Status Transition Transition Status 6 Role Resolution
- 7. Issue Resolutions Resolution Description Unresolved The default state of any issue. Resolved The issue is complete. Fixed A fix for this issue is checked into the tree and tested. Won't Fix The problem described is an issue which will never be fixed. Duplicate The problem is a duplicate of an existing issue. Incomplete The problem is not completely described. Cannot be Reprodued All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue. Limitation The problem won't be fixed because of some limitations. Not a bug The issue is not a bug. For example, it may be a usage or documentation issue. 7 The resolution is the final Issue state.
- 8. PO Requirement / Epic / Story / Improvement Workflow OPEN IN ANALYSIS READY FOR DEV CLOSED Create REOPENED PENDING IN DEVELOPMENT Start Analysis Complete Start Analysis Finish Analysis Start Development Stop Development Reopen Start Development Drop Drop 8RD Lead Any
- 9. OPEN PENDING REOPENED CLOSED RD ASSIGNED IN PROGRESS DESIGN REVIEW CODE REVIEW & FIX INFO REQUIRED FINAL REVIEW Task & Bug Workflow Create Reopen Complete Drop Drop Start Progress Start Progress Stop Progress Confirm Info Require Info Assign Assign Require Info Approve Ready for Review Reject Design Review Code Review Drop UID 9
- 10. Design Workflow OPEN PENDING REOPENED CLOSED ASSIGNED DESIGN REVIEW Create Reopen Drop Start Progress Start Progress Stop Progress Assign Assign Reject Design Review IN PROGRESS Complete Drop UID 10
- 11. 11 Separate Dev Issues and QA Bugs Development QA Bugs Epic Story Task Bug Design Requirement Improvement Bug PROJECTISSUES
- 12. Bug Workflow for QA OPEN REOPENED CLOSED Confirmed Create Reopen Confirm Confirm WAIT FOR VERIFY Fix Approve QA RD Lead Drop Reject 12
- 13. 13 Scrum Board & Reports
- 14. 14 Epic Filters Epic Link
- 16. 16
- 17. 17
- 18. 18 Good Practice
- 19. Good Practice ✓ Everyone can create requirements and bugs (from templates). 19 ✓ Stories, improvements, and bugs should be ordered by priority and ranking. ✓ Detailed specifications should be documented in Confluence. ✓ Update the issue when it goes to next progress. ✓ Update the issue estimate when it delays. ✓ To make the process work well, everyone should actively follow the workflow. ✓ Label issues to make the Scrum board easier to quickly filter specific issues.
- 20. 20 Thank you