Restrict Fix Version Creation

Does anyone have any ideas of customization or scripting we could do to restrict Fix Version creation? We've never been a fan of the fact that creating versions and components is a project admin permission, but it's even worse now that they added inline/on the fly creation. Before the update, many of our project admins didn't even realize they could add versions and components, but now it's significantly easier to do. 

If there's no hope of restricting the creation, does anyone have an idea for a script or something that would notify us when new versions/components are created? That would at least help us get rid of versions that shouldn't have been created. We have almost 150 projects so it's pretty difficult to just check each project regularly. 

Thanks for any help/ideas!
Keri 

 

1 answer

1 accepted

1 vote

I'm afraid there's not a lot you can do about this.  My impression is that most project admins appreciate it because it means not having to dig through admin screens every time they need a new version/component, so it's not much of a surprise that it's always enabled.  (I've not run across anyone who dislikes it, and plenty of people who were yelling for it before it arrived).  That said, for the handful of sites where it is a problem, it would be nice to have an off-switch.

I don't think there's anything you can do with components, but it feels like they are less of a problem than versions from the other times this has come up.

But for versions, a bit of code can be really handy.  Note that it's not "fix versions", just "versions" - fix, affected and custom versions all read the same list of versions for the project.  The creation of versions fires an event (I think you need to be on JIRA 6.3 or above), which you can catch with a "listener".  If you're writing a listener, you can do anything you want in there - the obvious option is to email people, but you could do pretty much anything.  As you mention scripting, I'd lean towards doing it with the Script-Runner addon, as usual.

Hi Nic, I appreciate your response. I can definitely understand how it could be useful, it just unfortunately doesn't work well with how we manage versions. Components definitely are less of a problem than versions. I'm not that familiar with scripting but I frequently use the built-in scripts from Script-Runner. I will try messing around with it and see if I can make a listener, as that would help somewhat. Thanks again! Keri

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,211 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot