You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?