Assignee, due date and components
A template, and each of its child work items, can also set three fields. They are under the labels and priority in the editor, and in a child's Details.
- Assignee: Jira's default (the project's default assignee, if it has one), unassigned, or the person using the template. No one is chosen by name: the app reads who is using the template at that moment and does not keep it.
- Due date: a number of days after the work item is created, from 0 (the same day) to 365.
- Components: by name, comma-separated. Each project has its own components, so they are matched by name in the project the work item is created in. A name the project does not have is left out, and the page says so.
A pick on the Templates page fills them into Jira's Create dialog, where the person can change them. "Unassigned" applies to child work items; in the Create dialog the app leaves the assignee as Jira sets it. Child work items get their settings when they are created. If a work type's create screen lacks one of these fields, or Jira will not assign the person, the item is created without it and the result says so.
Custom fields
Under Add a custom field, the editor offers the custom fields on the chosen projects' create screens that the app can set: short text, paragraph, number, date, dropdown and radio buttons, multi-select and checkboxes, labels and URL. A child work item offers only the fields its own work type has. User pickers, cascading lists, teams and app fields are not offered.
- A date is a number of days after the work item is created.
- Options are kept by name, so the same template works in projects whose fields have their own option lists. A Templates page pick looks the option up in that project; an option the project does not have is left out.
- If Jira refuses a value for a child work item (the field is not on its create screen, or the option is not available there), the item is created without it and the result names the field.