restrict components to single choice

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.

4 answers

1 accepted

This widget could not be displayed.

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.

Updating workflow will be a issue here; any way to do this by 'Behaviour or script runner'?

This widget could not be displayed.

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?

This widget could not be displayed.

Unfortunately, expensive addons are not an option for some JIRA admins, and may lead to problems with urgent JIRA updates.

Any way of doing this without addons?

This widget could not be displayed.

I think I have a relatively simple way to do this: 

  1. Create a single-choice custom field whose options match the project's list of Components.
  2. Put the new custom field on your Create screen, and the Components field on your Edit/View screen.
  3. Make the custom field required, and the Components field optional.
  4. Add two post-functions to the **beginning** of the Create transition:
    1. Copy from field to field (I think this is a JSU function) and copy from custom field to Components.
    2. Assign to Lead Developer.

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.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published Apr 22, 2018 in Jira Software

How-to setup a secured Jira Software 7.9.0 on Ubuntu 16.04.4 in less than 30 minutes

...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...

1,027 views 5 9
Read article

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