Is it possible to restrict the components field to be a single choice?
The reasons is for GreenHopper. We have scrum boards which key off components. When users select multiple choices, the ticket (story) is visible in 2 boards. Then 1 story gets put in an active sprint and locks out the other team from starting a sprint, because they see the 1st teams sprint with that overlapping ticket.
That is actually the core problem. But if you can answer my question, or give workarounds, that'd be helpful.
Atlassian support gave a pretty good workaround
Add an additional validator in the transition to check only a single selection is made for the component. Use the validator "Field Has Single Value" JIRA Misc Workflow Extensions for this.
Its a tedious if you have alot of steps, but does work.
i don't think components can be restricted to a single choice only.
but board filters can be modified.
so if Board1 never handles issue where Component1A and Component1B is chosen add
AND component not in (Component1A, Component1B)
will this work for you?
I think I have a relatively simple way to do this:
Make sure the spelling of the options in the custom field matches the Components **exactly** - eg, no trailing spaces.
Downside is you'll have to keep the custom field options in sync with the Components list.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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!
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