Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Problems with STAGIL Issue Templates plugin


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.

  • As a Jira admin, why am i not able to edit or configure existing templates? In addition to this, why are the creators unable to do the above as well? Are templates non-configurable once in use? 
  • Why when creating templates with a selection of configured fields, do these fields not stay consistent when other end users select the template? The end users are members within groups that the template is shared with so i would expect the same configured fields to show for them rather than all fields within the Jira screen?

Can anybody advise on either of the above?

Thankyou in advance.

1 answer

Hi UKIS SDLC Tools Team,

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

Best regards
Björn from Team STAGIL

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events