Problem: I would like to institute a rule for my teams, "One component per issue", and I do not see a setting, in the administrative section of JIRA, to implement this.
Relevance: Many of our reports look into the breakdown of any given project's work by component, having multiple components per issue can, ever so slightly, misrepresent those reports.
Comments: I know I can skirt around this problem by creating a custom field but, when you are in a JIRA project, it is nice to be able to click on the puzzle icon in the sidebar and view issues by component.
If you were on Server, there's a hack you can apply to the field template which converts it to single-select. (It remains a multiple entry field in every respect, but the users can't put more than one option into it)
Cloud does not support that. Go with the custom field option (and maybe use components for something else)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
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