Transition to More Powerful Jira Workflows
- 2. Product Strategy ◈ ◈ ◈ ◈ Customer Experience ◈ ◈ ◈ ◈ ◈ ◈ Partners ◈ ◈ ◈ ◈ Agile Delivery ◈ ◈ ◈ ◈ ◈ Cloud ◈ ◈ ◈ ◈ ◈
- 3. ◈ Save your users time ◈ Keep your data accurate ◈ Use Transition Screens ◈ Use Transition ‘Options’ ◈ Properties ◈ Triggers ◈ Conditions ◈ Validators ◈ Postfunctions
- 6. 1. Create Screen 2. Include Fields that will help users enter necessary data 3. Edit Transition to select screen
- 10. Properties - are key-value pairs that can be used to further customize transitions Triggers - initiate a transition when an event occur in Dev tools Conditions - hide a transition if user is not allowed to perform Validators - check that input is valid before the transition is performed Post-function - carry out additional processing, after a transition is performed
- 12. 1. View Workflow in Diagram layout 2. Select Edit 3. Highlight the transition
- 17. To transition Jira issues when certain events occur in connected development tools ◈ Keep your issues synchronized without relying on manual updates by dev ◈ Must have at least one dev tool: ◈ Fisheye/Crucible ◈ Stash ◈ Bitbucket ◈ GitHub
- 18. 1. View Workflow in Diagram layout 2. Select Edit 3. Highlight the transition
- 22. To control whether a transition should be executed by the user. If a condition fails, the user will not see the transition button on the 'View issue' page, and so will not be able to execute the transition. ◈ allow only the reporter to execute a transition. ◈ allow only users with a certain permission to execute a transition. ◈ allow execution only if code has, or has not, been committed against this issue.
- 23. 1. View Workflow in Diagram layout 2. Select Edit 3. Highlight the transition
- 24. Only a developer can move an issue to ‘In Review’
- 25. ◈ ‘Any’ or ‘All’ ◈ Grouping - multi-level ◈ Transition won’t be see by user if they don’t qualify
- 29. ◈ Check that any input to the transition (for example, by a user) is valid, before the transition is performed. ◈ Input can include that gathered from the user on the transition screen. ◈ If a validator fails, the issue does not progress to the destination status of the transition, and the transition post functions are not executed.
- 34. To carry out additional processing, after a transition is performed. ◈ updating an issue's fields ◈ generating change history for an issue ◈ adding a comment to an issue ◈ generating an event to trigger email notifications
- 36. ◈ Move added Post Functions down so they are executed just before the event fires ◈ Set the resolution when an issue is done ◈ Clear the assignee when an issue is done ◈ Clear the resolution when an issue is reopened ◈ Modify the event from ‘generic’ to ‘closed’ or ‘reopened’
- 38. ◈ Don’t over-automate ◈ Always look at ‘Conditions’ first if a user can’t see a transition ◈ Plenty of Add-Ons in Marketplace
- 39. Browse Atlassian Marketplace for add-ons that will benefit your teams
- 40. ◈ Save your users time ◈ Keep your data accurate ◈ Use Transition Screens ◈ Use Transition ‘Options’