Are Projects anything more than Jira-specific links?

[Keith Furnell]

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/

[Jeff Madison]

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:

1. Recently used by me (past 24 hours only)
2. Linked to this project
3. Everything else. Maybe don't show these until you hit a button.

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.

[Keith Furnell]

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.

[Hitesh Sethiya]

Hi @Keith Furnell 

Linking Projects to Compass components on the Overview page establishes a connection between a Jira project and the component, which helps power work suggestions on the Development tab in Jira.

@Jeff Madison That's a great idea! We will definitely consider improving the components dropdown experience in Jira.

[Keith Furnell]

Thanks @Hitesh Sethiya

I'm familiar with Jira's Development panel, but not the Development tab - could you provide a documentation link for it and perhaps give an example of ways that this link from Compass powers work suggestions there?

Also there are quite a few Atlassian Team responses like yours on this forum implying that a suggestion will be taken on board, but no obvious records added in https://jira.atlassian.com/projects/COMPASS/issues/. Is their state visible anywhere else?

[Hitesh Sethiya]

Hi Keith, 

I apologize, I just realized that the Development tab in Jira is in closed beta and will be further rolled out to all customers in the coming months. 

I've created COMPASS-118 to track the components dropdown change.

[Keith Furnell]

Isn't COMPASS-118 describing current behaviour ?

Improve the Components dropdown in Jira to prioritize components based on recency of usage, while still allowing access to all components.

This seems to be missing the point about also prioritising components that are linked to that Jira project (similar to this change).

Out of interest does the beta Development tab also address https://community.atlassian.com/forums/Compass-questions/Component-catalog-breakdown-by-attribute/qaq-p/2983945 ?