STM for Jira Cloud and Data Center
Easily manually/auto create/transition issues (subtasks, Linked or Epic Issues). Define templates for commonly created details
Easily manually/auto create/transition issues (subtasks, Linked or Epic Issues). Define templates for commonly created details
Use Cases
1 - On-board New Staff
Problem
Company Xyz on-boards new staff by creating a new ticket for each part of the on-boarding process (i.e. Setup email address, setup phone…). The current process involves creating 68 sub-tasks issues under a common parent. Creating all those tickets is a very time consuming task and often leads to errors.
Solution
High Level Overview
Use STM to create a Template specifying all of the details for the 68 issues that need to be created. Create an STM Executor that will create that Template, when a new Task issue is created in the Project. This will give the same consistent set of sub-tasks every time.
Technical Details
Create a STM Template that contains all 68 sub-tasks, filling in the summary, description, assignee… for each issue as well as which fields should be copied from the parent issue to those sub-tasks.
Set up a STM Executor to watch for the new Tasks being created in the OnBoarding project. When the Executor detects a new Task, it automatically creates all issues defined in the Template as sub-tasks, copying any parent values
Variations of this
- Create Epic Issues or Linked Issues instead of the Sub-Tasks
- Creating the Issues when changing the status, for example when it changes to “In Progress”.
- Creating the Issues when a particular field value has changed (i.e. when assignee has been added)
2 - Process Support Bugs
Problem
Company Xyz receive bugs through a JSM portal. When the bug has been verified, the user needs to create 5 sub-tasks that will ensure that: the bug is fixed, unit tests are updated, the code is reviewed, a pull request is created and the code is merged
Solution
High Level Overview
Use STM to create a Template specifying the 5 sub-tasks and their required values. Create an STM Executor that will create that Template, when the Bug ticket is changed from To Do to In Progress. This will give the same consistent set of sub-tasks every time any Bugs are moved from To Do to In Progress.
Technical Details
Create a STM Template that contains all 5 sub-tasks, filling in the summary, description, assignee… for each part of the bug fixing process.
Set up a STM Executor to watch for when tickets with the Issue Type Bug are moved from the To Do status to the In Progress status. When this occurs the 5 issues in the template are created
Variations of this
- Create Epic Issues or Linked Issues instead of the sub-tasks
- A Transition Executor could be added so that when the last sub-task is transition to Done then the parent bug will also be transitioned to done.
- Change the Executor to Create the sub-tasks when an assignee is added