Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

4 votes
Answer accepted

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'?

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.

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?

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?

Were you able to find a solution to this without having to use add-ons?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

3,742 views 5 15
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you