nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to associate multiple compass components to a single Jira issue?

Nate Whitehead

It looks like the compass field in Jira only allows for a single component to be selected. Is there a plan (or am I just missing where to enable this) to have the field able to select multiple values? Also, when will Jira be able to have custom fields created associated to Compass values?

Accepted answers

All comments

Katie Silver

Hey @Nate Whitehead , great questions. We're working on multiselect as part of the next phase of field improvements which we hope to have out sometime this summer (US time.)

Can you tell me more about your second question? Custom fields related to Compass values, how are you thinking about using this?

Nate Whitehead

Thanks Katie. I can envision people using Compass components as a field in different ways like "Impacts library", "Needs Service", "<verb> <compass object type>". Given that we have >1000 projects/teams using Jira, there's going to be more than one definition for "what" the compass field implies - and in some cases I could envision a team needing to indicate one compass component for one 'verb' and another compass component for another.

Katie Silver

Got it. This is super helpful! Thanks for the detail 😀

Holger Winkelmann_m23766

We have the same issue, and like to link multiple components to a Jira issue, basically the same multi select the internal components in Jira have