Is the Projects field of a component's Overview purely informational? It doesn't, for example, appear to have any bearing on the Issues page.
Where Compass components are used in Jira, the Components field selection appears to be global across Jira projects. Is there any intention to use the populated Compass Projects to limit the Jira Components presented for selection?
Related documentation: https://support.atlassian.com/compass/docs/link-jira-issues-to-components/
It would certainly be nice if the Components dropdown in Jira gave higher precedence to components explicitly linked to the current project. Today it appears to be a global list but with the most recently used ones at top, which is better than nothing. Personally I'd like it to have three sections in that dropdown:
I do think having all the components (even those not linked to this project) available in that list makes sense because sometimes a team will be doing work on some other team's components, either because of inner-sourcing or just because life gets messy. But that is probably the 5% use case while the 95% use case is ones linked to the current project. IMHO anyway.
Precedence sounds good to me. It'd be good if #2 & #3 were distinguishable (e.g. in results once you start typing). Worth noting that Compass, presumably deliberately, allows components with the same name, which I guess might make sense across distinct Jira projects or teams.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.