Releases/Versions in Compass?

Question

Is there a way to manage versions in Compass? Specifically in such a way as for these versions to be made available in Jira so that work can be assigned to them?

Open to guidance from anyone using compass and working with releases/versions/deployments.

Joe Lawson · Answer

yes

Andrei_8eecdk · Answer

[C]ompass components themselves would be where all of this was centrally managed and version/release/deploy artifacts would be made available in Jira issues when a component was specified

So rather than having the versions / releases managed in Jira ( i.e. https://support.atlassian.com/jira-software-cloud/docs/create-a-version-in-a-classic-project/ ), you'd rather have that process be managed in Compass?

That is to say, having a version be able to get created from a Component page, having issues be able to target that version, and then surfacing the release on the activity timeline. Does that about cover what you'd be looking for here, or am I misunderstanding?

Right now, Compass components do get surfaced as components in Company Managed Projects in Jira, but we don't really have a robust representation of releases in Jira as they pertain to a specific Compass component.

Would you be able to share the sort of information you'd like to have available on the Compass component view pertaining to versions and releases?

Matt Richards_q2q9cg · Answer

Thanks for the quick response. Apologies for the delay.

We are looking for a centralized way in which to manage versions/releases/deployments in our Atlassian toolchain. In our opinion ideally Projects/Teams in Jira wouldn't have versions/releases/deployments in and of themselves. Rather compass components themselves would be where all of this was centrally managed and version/release/deploy artifacts would be made available in Jira issues when a component was specified.

If not in this way, how does Atlassian expect versions/releases/deployments to be managed today?