Atlassian Team members are employees working across the company in a wide variety of roles.
April 16, 2024 edited
Hi @Mario Cappellano , unfortunately not yet! I would love to add Compass to service-type projects. I would encourage you to comment in the Jira Service Management community group with the feature request. I'll add it on my side, but we will need the JSM team to prioritize it as well as us.
@Katie Silver Currently I use Jira Components in a system implementation project (JSW) where we are implementing a vendor software package (not developing in house). I use components to categorize our work based on the "aspect" of the software, rather than actual modules, libraries, services, etc. Here are some examples:
Analytics
API
Recipe Authoring
Business Process
Collaboration
Compliance
...
So in summary, they are more like functional areas or subjects. We do also use components for actual real things, like the software's integrations with external services (e.g. Oracle).
I'm just concerned that by moving to Compass components, these "aspect" components will not have a place in the new kingdom. And if the do (I've seen the "Capability" and "Other" types), I don't necessarily want them shared across other projects, or even tracked in Compass. I don't need analytics for up/down time, failing tests, etc on those, because they are more about features rather than hard-line boundary systems. Sorry if I'm not making any sense. Do you have any ideas?
Being able to use both Compass Components and Jira Components is essential for our organization as we manage multiple large initiatives across multiple Value Streams. Compass Components would allow us to create global Components to indicate that Epics and Stories relate to one of these cross-Value Stream initiatives. While Jira Components enable teams to manage their own library of Components that are unique to their work and process.
If you would like to express your interest in an enhancement that would allow Compass Components and Jira Components to coexist, please add your vote to this ticket:JRACLOUD-83736
This is a really good question. You're definitely not alone in your scenario. Totally makes sense the way you described it.
I think ultimately this is going to come down to how Atlassian defines "Components" going forward. The long term strategy is to evolve Components into this very software-oriented model; that means we will need to find a solution for users like yourself who use Components for a different purpose.
I'm wondering, have you tried using Custom fields - specifically, an option (select) field? These fields can have different values for different projects. They don't have the built-in automation that the Components field has (Default assignee) but they do work with Automation in Jira as a workaround.
I'm curious what you think - let me know. We're still working on how to move forward and I want to make sure this use case is addressed appropriately.
I'm having problems using JQL to filter out services using the new Components from Compass. The JQL is returning tickets using the old components also because the name of the component is the same.
This is a problem if we need to perform any corrections in Compass (e.g., remove a component, and link to the right component).
Is it possible to get a JQL that excludes values from the old version of Components?
1. You've blocked me from creating new components in new projects without using Compass (which doesn't actually add any new functionality?) - how do I get around this?
2. If and when I'm able to opt-out site wide, does that prevent me from using Components as I have before? If so that's less functionality for the same cost - not good.
3. Why are Atlassian so focussed on adding stuff that adds little to no value (Atlas, Rovo, Compass) when the Cloud platform is so unstable / slow when compared to the data centre / on prem version? You need to get the basics right before you start trying to increase revenue - open source solutions like Open Project are getting better, Atlassian cloud is getting worse - that can't be good.
You can opt out of Compass components at the project level (via a project admin) or set a default to Jira components at the site level (via a site admin.) Instructions are here: documentation. There are no restrictions on using Jira components and no extra charge for doing so - Compass components are just an option.
I'm sorry to hear you don't feel like these additions are valuable. We know they're not for everyone, that's why we made them optional. I can't speak for the teams working on the Cloud platform but I am sure they monitor the community as well, and I can take your feedback to our team.
33 comments