Issue and Work Item Templates by Eolivion
Issue and Work Item Templates by Eolivion fills in a work item from a template and creates its subtasks and child work items, in the order you set, with the links between them. It can assign each item from a people field, and create a work item from a template on a schedule. It runs inside Jira and makes no calls to outside servers.
Set it up (Jira admin)
- Go to Settings > Apps > Issue and Work Item Templates.
- Under The Template field, tick the projects that should use templates and choose Create the Template field. The app creates a field called Template and adds it to those projects' create screens.
- Choose New template, or open a work item that's already set up the way you like and save it as a template (see below).
Team-managed projects don't share screens, so the app can't add the field there. People in those projects use Apply or save a template from the work item's ••• menu instead.
What a template holds
- The work item itself: a description, labels and a priority. If someone already wrote a description, the template's goes below it. Labels are added, and the priority is only set if nobody picked one.
- Items to create, in order: subtasks, and child work items for parents that can hold them, like an epic. Each one can have its own description, labels, priority and assignee.
- Links between items: for example, "Kickoff call blocks Set up access".
- Where it applies: the work types and projects that can use it. None ticked means all of them.
In the description, "## " makes a heading, "- " a list and "[ ] " a checkbox the team can tick off in Jira.
Use a template
When you create a work item: pick the template in the Template field and create it. A few seconds later the work item is filled in and its items are created under it.
The Template field only shows in the create window's full view. If your create window opens small, choose ••• > Full view once; Jira remembers it.
On a work item that already exists: open it, choose ••• > Apply or save a template, pick the template and choose Apply.
It also works when a work item is created by an automation rule or another tool, as long as the Template field is set.
Save a work item as a template
Open a work item, choose ••• > Apply or save a template and then Save this work item as a template. The app copies its description, labels, subtasks and child work items in their current order, and the links between them. Change anything before saving.
Jira admins can manage every template. Project admins can save and change templates that apply only to their own projects.
Who gets each item
Each item in a template has an Assignee:
- Unassigned.
- Whoever created the work item.
- The work item's assignee.
- From a people field: the person in a field of the work item, like "QA owner".
- One copy per person in a people field: the item is created once for each person in the field, each copy assigned to that person and named after them, like "Review: Ana" and "Review: Bruno". Copies go in alphabetical order, up to 50 per item.
For the last two, you pick the field from a list. Team-managed projects have their own fields, so the list shows which project each one belongs to. When a template is used in another project, the app looks for a field with the same name there, and if there isn't one, the work item says so.
When the field is empty, the item is created unassigned or not created at all; you choose which for each item. When someone in the field can't be assigned work items in that project, their item is still created, unassigned. Apps in the field are left out. The work item lists every one of these cases when the template is done, so nobody has to guess why an item is missing.
Create on a schedule (Jira admin)
For work that comes back every week or month, like a weekly close or a monthly report, the app can create a work item from a template on a schedule. Each time it's a fresh work item from the template, with its items and links, not a copy of the last one with its old comments and status.
- Go to Settings > Apps > Issue and Work Item Templates and, under Scheduled, choose Schedule a template.
- Pick the template, the project and the work type, and write the summary. Tick Add the date to get summaries like "Weekly close, Nov 3".
- Choose when: every weekday, on some days of the week, or once a month on a day, the first workday or the last workday. Set the time and the time zone; it follows daylight saving time.
- If you like, set a due date a number of days after it's created, a date for the schedule to end, and who gets it: one person, or people taking turns.
The work item shows up within five minutes of the time you set. Day 29, 30 or 31 runs on the last day in shorter months.
Create one now makes one right away, to check it looks right, without changing when the next one comes. If people take turns, it counts as a turn.
You'll be the reporter of the work items a schedule creates. If you can't create work items in that project anymore, the schedule pauses instead of creating them for you, and the list says why. It also pauses if the template is deleted or the project loses that work type. To take over someone else's schedule, open it and save it; you become the reporter. If the person whose turn it is can't be assigned work items in the project, that one is created unassigned.
Order and reliability
Items are created one at a time, in the order of the template, each one already under its parent. If Jira asks the app to slow down, it waits and tries again instead of skipping the item. When it's done, the work item shows the result, for example "Release epic applied: 60 of 60 created", or which items failed and why.
Automation rules and usage
The app creates the items itself, not through an automation rule, so applying a template or running a schedule doesn't use any of your Jira automation usage.
Your own rules still see the new items like any other work item. If you have a rule that runs when a work item is created, it also runs for each item the template creates, and those runs count toward your usage as usual. A template with 60 items means 60 more runs of that rule. The app shows up as the initiator of those runs, so if you only want the rule for work items people create, add a condition on the initiator.
Permissions and data
The app creates and edits work items itself, and sets the person who created the work item as the reporter of the new items. Work items from a schedule have the person who saved the schedule as their reporter. Before applying a template from the menu, it checks that the person can edit the work item and create work items in the project. Templates and the result of each run are kept in Atlassian's own storage for the app; see the privacy policy for exactly what's kept.
Need help?
Open a request on the support portal or write to support@eolivion.com.