SinceJira hosting: Server, Data Center (since: v6.3.0. Jira hosting: Server, Data Center
...
), Cloud (since v2.7.3)
Scheduled Issues can be used as templates, you can use it them for your own tasks or use scheduled issue as a team task template.
If you share template among team members, you probably need to do a lot of editing especially in user- user related fields like : Reporter, Assignee, or some Custom user picker fields. Or maybe each of your team members have almost exact same tasks with only the difference in Assignee.
We came up with a solution for that!
With v6.3.0, each Each of the user picker fields in the 2nd step of the wizard, have a checkbox to “Set current user as ‘field’ on manual executions”. If you check it under Assignee field, then when Scheduled Issue is manually executed, the user who triggered the creation of Jira issue will be set as an Assignee and also should be set in the visible on the screenshot “Custom User Picker”.
...
| Info |
|---|
To search for issues created with The Scheduler you can use our: Dedicated JQL functions |
Use Scheduled Issue as a template and create issue in the desired status
Moreover, with new feature of setting up the initial status … your users can use those templates right away and when they create the issue it can be transitioned to the 'In progress” status.
Let Let’s see this in action, here . Here we change only 1 thing in the template:
...
Now lets let's execute it, by the same users, in the same order. This time let’s see this in Execution history dialog (notice “See in issue navigator” link):
...
Here is one of the best outcomes of combining both of this these features, if you are using e.g. kanban board, issues after manual execution will end up in the correct column and save you lots of editing:
...