G'day all,
I have an situation where by for one give issue type I need to not allow a given version/release to be specified for any of the release fields. (Affect/s version, Fix version/s, our custom version/release types)
The only way I could think of is essentially each transition throughout the workflow create a script runner validator for each release field type that ensures the incorrect version was not chosen.
I have two concerns with that solution. 1. It is long and will be a pain to maintain as it is several validators on every transition. If a new transition is added it must get all the validators, etc. 2. It really only prevent transitioning with an incorrect release, I would really prefer the release not even be visible in the selection.
I would think others would have this problem/need as well, as I see this as a somewhat common problem, limiting version based upon issue type.
Any help is always truly appreciated.
Thanks,
Robert
Hello,
Try to make a ScriptRunner behaviour if you are not on Cloud.
https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html
Behaviours can hide field in UI.
Awesome!!! Did not know about behaviors... I will give it a try and mark it answered if it works!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh I see behaviors can hide the entire field but not limit it to not have a certain value. So I want one of the versions (call hotfix) not available for the hotfix issue type. SO Hot fix is both a version in project A and an issue type. If we are in the issue type hotfix making affects version hotfix makes no sense but people are still using it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.