Coming this December: a new and improved integration between Compass and Jira Software

[#1]

Happy Friday, Compass users!

We’ve heard your feedback loud and clear: the current Jira Software integration can be slow, complex to set up, and, in some cases, conflicts with how you are already tracking work against software components.

This initial version of the integration helped us understand how you want Compass and Jira Software to interact. But now, it’s time to level up.

What's new? 

An improved components experience in Jira Software

The next version of our integration significantly improves your user experience by using the existing Components field on Jira issues, and by working in all the places in Jira Software where you’d expect (emails, import, bulk edit, search, and more.) You will be able to tag Jira issues with multiple Compass components. We’re also releasing a brand new version of the Components page that pulls important data straight from Compass into Jira, so you don’t have to leave the product to find what you need. This will start as an opt-in experience so you have the time you need to adjust to the change. 

---

Create Jira issues for failing scorecards

Soon, you can more easily track and fix failing scorecards by creating Jira issues in your team’s backlog. These issues will also appear on scorecards in Compass. This helps your teammates work towards improving their DevOps metrics, and communicates their progress.

---

This integration is in active development, and you can expect regular updates as we get closer to launch.

• Create Jira issues for failing scorecards is currently scheduled for an October release.
• An improved components experience in Jira Software will ship sometime in December, with 100% of you getting access by mid-January.

There will be opportunities to get involved early with the new components experience, including a way to opt-in to the first cohort of sites with access, and ways to give feedback directly to my team.

FAQ

• If you use the Compass custom field, today, nothing changes. When we launch the new components experience, we’ll provide instructions for migrating and a timeline for deprecating the custom field. We’re doing our best to make this as easy as possible for you, and we promise we won’t turn it off without a lot of notice.

• If you use Team-managed projects in Jira, you’ll see the new components experience a bit later. The integration is only going to work in Company-managed projects at first. This is because Components don’t currently exist in Team-managed projects today. We’ll follow up and add support, but in the meantime, you can continue using the Compass custom field if you’d like.

• If you already use the Components field already to track software architectural components, good news! We’re going to align to your way of thinking. The most important thing for you to do is make sure all of your current Components are represented in Compass. Once we turn our new integration on, you can start using Compass components the same way as you use Jira ones today.

• If you use the Components field for a different purpose today, don’t worry - we’ve got you. We’re working on an easy process for moving your data out of the Components field and into another, probably to a custom field that has the same functionality. More to come on this front, so you can trust that we’re looking out for your use case.

• Have opinions, feelings, feedback? Please share with us! We want this integration to work for you. Add comments to this page or contact us through Intercom directly inside of Compass.

Thanks everyone, hope you have a great weekend,

Katie - Compass PM

[Holger Winkelmann]

@Katie Silver Thanks for the update, would like to join the component opt in.

[Nate Whitehead]

Looking forward to this, thanks for the update @Katie Silver 

[Katie Silver]

@Holger Winkelmann @Nate Whitehead I just posted a link to the signup form - would you mind filling this out for me, so we know what site to activate the integration on? 

Sign up link for early access to Compass x JSW integration 

[Holger Winkelmann]

@Katie Silver as requested, form filled. 

[Katie Silver]

amazing, thank you! I'll be in touch soon with next steps :)

[Helmut]

@Katie Silver How can one search for all Jira issues linked to a Compass component via the Jira REST API and JQL, leveraging the *id* of a component, given the name of a component might change?

[Hitesh Sethiya]

Hi Helmut,

JQL doesn't support searching by IDs.
With Jira REST APIs, you can get paginated components and use the names of these components to search through issues using the Issue-Search API.
However, if a Compass component and a project component have the same name, you might end up with results with either of the components linked to an issue.