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?
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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Got it. This is super helpful! Thanks for the detail 😀
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey guys, quick update from our side - we are expecting to ship the first version of this work sometime in November. We're doing a huge overhaul of how Compass components work in Jira, and multi-select will be included (along with bulk edit, dashboard functionality, and other things you expect in Jira.) More to come soon, I'll make a post when we get a few more details nailed down.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, then we will wait for this before starting with compass. Otherwise our component concept will break and add cognitive load for the team going back and forward
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
makes sense - I'll keep you posted!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi friends, check out the feature preview here: https://community.atlassian.com/t5/Compass-articles/Coming-this-December-a-new-and-improved-integration-between/ba-p/2498839
This new integration will support multiple components per issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wow, is there a new, better Atlassian dev lifecycle? Really impressed about the speed in compass development and Jira integration
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ahh it makes me happy to hear you say that! Because we're a smaller product, Compass is able to move very quickly - we ship new features typically every sprint. I will say this work with Jira has taken us a bit longer than we expected, but it's worth it because this integration is going to be a huge step up. Glad you're interested :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.