Looking to get some answer relating to the functionality of the 'STAGIL - Issue Templates' plugin within Jira Server. As a Jira administrator, i've been getting an increasing number of queries relating to this plugin ranging from permissions within templates to configured fields not saving within the template after creation.
We are currently running on version 3.0.57. From looking at the latest version (3.0.58), i cannot see any improvements or changes that would be causing the following two points i would like clarified.
Can anybody advise on either of the above?
Thankyou in advance.
1. In the latest version you can add contexts to templates. Project admins are then able to manage the templates within their project context. Also we are currently developing the option to add editor group to templates as it was released by Atlassian for Jira filters last year.
2. Not all field types are supported in templates but the number of supported fields is growing steadily. In the latest version we fixed a bug where unsupported fields have been shown in the template definition. This might have resulted in the described misbehavior.
For support you can reach us via email@example.com.
Björn from Team STAGIL
Calling all collaborators and Confluence users! Our Appy Hours event on September 29th features 4 presenters demoing functionality to superpower Confluence. Don't miss learning about these apps i...