For JIRA Cloud users, how are you restricting Components to a single component field?

We have been struggling with this and I see many users are struggling with the same.  We need to set various other fields based on a single component value.  The most complete solution appears to be with using Script Runner/  the Server version of JIRA.  For JIRA Cloud, I do not think behaviors is yet implemented with the Script Runner add-on.  We are trying some solutions with the utilities single field transition validator and post functions using JMWE but since this is transition based, on Edit, additional components can be added.  This is messy for users because on transition, the multiple components will be flagged for correction.

We have also considered making a single pick list custom field for components and then in post function update the JIRA component field to the selection.  This has other negatives.  We would need to keep the pick list in concert with the component table and also see if we can script the auto-assignments on our own?  

Are there any cloud version add-ons that we should investigate?  What solutions are other using for similar needs with the components field?

0 comments

Comment

Log in or Sign up to comment
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

449 views 7 5
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