Known Limitations
Our team works on the ability to support all available Jira fields, but at this point, there are some limitations with data will be saved in your template or hierarchy node.
Fields usage with Templates and Hierarchy Nodes
Field Name | Templates | Nodes | UI Modifications |
|---|---|---|---|
Summary | |||
Description | |||
Assignee | |||
Labels | |||
Paragraph | |||
Short text | |||
Date | |||
Time Estimation | |||
Priority | |||
Severity | |||
Components | |||
Time Stamp | |||
Number | |||
Story points | |||
Dropdown | |||
Checkbox | |||
Dependent Dropdown | |||
Multiple users selector | |||
Multiple groups selector | |||
Linked Issues |
|
|
|
Epic Link |
|
|
|
Parent |
|
|
|
Attachments |
|
In case the field is not supported by templates or hierarchies, it is still possible to use it - SITC does not change the Jira issue type schema and unsupported fields can be filled manually after the template/ hierarchy application.
Assignee and Reporter fields:
The user who is selected in the Assignee and Reporter fields of a Template\ Hierarchy Node should have access to the project you wish to apply it to - the Smart Issue Templates don’t change the Jira Permissions and Product Acess options.