You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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 firstname.lastname@example.org.
Björn from Team STAGIL