This "new" feature is completely opaque. No where are there notes on what differentiates the two concepts, other than if you use Compass components you can't use Jira components.
In my humble opinion, the new suggested usage of Components with a direct link to Compass is more suitable for Software development teams that think of their code repositories as services and can catalogue them into components such as Database, Front End and other parts of the software architecture.
I don't see this being very useful for more traditional business teams using Scrum or Kanban project templates to track their work and using Components to depict technology, workstreams or locations.
Remember you can always switch back to the traditional Jira Components.
Who uses Components for anything other than exactly what you say Compass is for? Our Components are like:
Middleware
Database
Frontend
Auth Services
etc.
Components already have owners, etc.
Can you give me examples of what Components you think people are using under the standard Jira components when you say "technology, workstreams or locations"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My perspective on Compass Components vs standard Jira Components, and I'm curious to hear from anyone here to check my logic.
SIMILARITIES: They are both objects. In both cases they can be used as objects to represent real world "parts of the architecture" or real world "part of value streams", or as slices of "anything" that is important to the people work on related issues. Component objects are great to use as metadata for reporting.
DIFFERENCES: The differences lie in the attributes that describe the object. Jira Components have attributes like; {name, description, component lead, default assignee} Compass Components have attributes like {name, description, owner, performance, dependencies, score card}. But the other major difference is the management dashboard for Compass Components has an "executive summary" look and feel, which is pretty neat.
A word about cost though, it looks like beyond a free trial, that only instance with 10 users or less can enter at the free tier for ongoing use, while instances with more than 10 users will pay $7 per user wrapped into their currently billing cycle.
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.