Is it possible to make values in Affected Version field conditional?

[Dan Deftos]

We have configured our projects to be team based and we have a team which works on multiple, lower level pieces of software. Each of these software components has it's own version nu.mbering scheme. For example, a dll might be 1.1.10 and a different dll or driver might be 5.2.3. We would prefer not to have to setup multiple projects in this instance. We would also like to ensure users/developers chose the correct versions for the software components they are working on. Ideally what we would like is to have a value in one field (Component) drive the available values in the Affects/Fix version field.

Has anyone done something similar, using the standard JIRA Affects/Fix version fields? I understand we could create a custom cascading select field but we would lose the standard functionality available with the Affects/Fix version field.

[Satyendra Narwane]

Hi Dan Deftos,

Yes you can do this with the help of Behaviour plugin(i.e Script Runner) by adding behaviour for the Affects/Fix version and you need to write groovy script which contains the business logic as per your requirement. Also you need to get the info from the database for the required field and push them to drop down value.

Actually we have develop one script for our client but we cannot publish it, so sorry for that.

Thanks & Regards

Satyendra Narwane

[Dan Deftos]

Thank you Satyendra. We will investigate our options via Script Runner. To date we have used the standard functionality provided by this plugin, primarily the predefined scripts and JQL fields. Leveraging groovy is something we will need to tackle next.

[Boris Berenberg]

There is no current way to do that. However, you could essentially hack the existing system by duplicating the component data into the Versions list. For example you have important.dll and important.driver  as components which are in 1 project. Then you would have a set of Versions that looked like this:

important.dll - 1.1.1.10
important.dll - 1.1.2
important.driver - 5.2.3 
important.driver - 5.2.4 

[Dan Deftos]

Thanks for the response Boris. What you describe is in fact our current implementation. We were hoping to improve the usability by making the screen a bit smarter. It seems that some customization via a plugin may be necessary.