Hi friends,
Thanks so much to those of you who signed up for the pilot group trying out our new Compass x JSW Integration.
For those of you who didn't sign up, don't worry! No hard feelings! We'll begin shipping the functionality to you this week. This is a progressive release, so it will take until mid-January to appear on everyone's site.
Here is everything you need to know about how to use Compass Components in Jira Software, and how it affects you.
When the feature appears on your site, you will see a new drop-down toggle in the Components page on your existing Company-Managed Jira Software projects. That toggle will allow you to opt into Compass components (or opt back out if you prefer not to use it on a given project.)
Any Jira component data that you've already applied to historical issues will be preserved - there's no risk of data loss. You can toggle back and forth as many times as you'd like.
New Company-Managed Jira Software projects will be created with Compass Components opted in by default. You can still opt out and go back to Jira components if you prefer. This change will only take effect in Jira Software projects - Jira Service Management and Jira Work Management are not affected.
Any user with JSW access can use the Component field. Only users with Compass access will be able to view the Components page information. Project Admin access is required to toggle between Compass and Jira Components (the same way that Project Admins manage components today.) The toggle works per-project, so you don't have to opt your whole site in all at once.
Learn more about:
What will it look like?
This is the first thing you'll see on the page - a spotlight highlighting the drop down.
Once you click through the spotlight, you'll see this toggle. Project Admins can click it to switch between Compass and Jira Components for their project.
Here's what the field looks like! When a user clicks on Components after their project is opted into Compass components, they'll see the full list of Compass components to select from. These will be sorted by relevancy, so the most-used components per project will be at the top of the list. It's also searchable.
The id-gatekeeper component with the icon is from Compass. You will recognize Compass components on issues because they always have an icon. If there is a historical Jira component value on the issue already, it will be grayed out. Finance is an example of a historical Jira component that was applied to an issue before Compass components are opted in.
Once your team starts tagging issues with Components, they'll be listed in the Components page. Ta-da! Note - the only way Components show up on this project (for now) is for them to be associated with an issue in that project. We'll work on adding other ways to list them here in future releases.
Troubleshooting
1. What if my components don't load into Compass? Try toggling back to Jira Components and then to Compass Components again. This should trigger another sync attempt.
2. What if I want to use components in Automation? For now, you won't be able to use Compass Components in Automation rules. This is due to some complexity in the way automation is built around components living in projects. We're going to work on this as a top priority and I'd expect updates sometime in the new year.
3. My old issues associated to the Compass custom field no longer appear in Compass. We are changing this experience for everyone to pull from the Components field for now. If you're having an issue where you need to use this page, but you don't have access to the feature yet, please leave a comment here and we can get you added.
How can I ask questions or share feedback?
Katie Silver
12 comments