nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira and Compass Components

Cate DiNoto

What is the most effective way to use Compass Components that are created in github, sync to Compass and are linked to Jira in Projects, Epics, Issues, etc. since in Jira Issues 'new' components can also be created but seem to be used primarily like labels? Would one ever overwrite another? It seems as though there is potential to have duplicates and confusion.

Recommendation and HELP documents appreciated.

Thanks!

Accepted answers

Timoti Sburv

The best way to manage Compass Components and Jira integration is to establish a clear workflow for syncing and linking components. Since Compass Components created in GitHub sync to Compass and can be linked to Jira issues, the key is to ensure consistency in naming conventions and avoid duplicate component creation directly in Jira.

Use Compass as the source of truth by maintaining all key components there and ensuring teams reference those instead of creating new ones in Jira. Also, restrict Jira component creation to avoid duplicates. Automate syncing by using integrations so that when a component is added in GitHub, it reflects in Compass and links properly in Jira.

Regularly review Jira components to align them with Compass and merge or remove duplicates when necessary.

All comments

Timoti Sburv

Regularly review Jira components to align them with Compass and merge or remove duplicates when necessary.

Cate DiNoto

Thank you for your reply Timoti, I will run your recommendation by the team.

This was the approach I was thinking would be best long term which will involve some clean up certainly as there was a significant period of Jira use prior to our use of Compass & doing App & other Component management there.

I still have a concern that for this use case it appears that information isn't sync'd between Compass and Jira.

a. starting in Compass, an App component has a Project link, perhaps multiple projects linked.

b. from Jira, when viewing a specific project that has been linked to the Compass App component (via Compass) the App component does not show up in the list when viewing via the left nav 'development\components' list.

Another observation if toggling between Jira components and Compass components -

a. in Jira component view, a list of components are displayed, because they'd been created in Jira.

b. also in Jira, when set to Compass components, after the App component was created in Compass (std. workflow; github repo sync'ing to Compass, linked to project, task, issue), it does not display in a list that is viewable in Jira, the screen is blank.

Is this just a setting issue in either Compass or Jira? Or is it only ever possible to have the list displayed if we toggle to Jira components?

Thanks again!

Timoti Sburv

Sounds like a visibility/config issue. Compass components won’t show in Jira’s native Components view unless the integration is fully set up and components are linked to the project. Make sure Compass is enabled in project settings, and switch to the Compass view in Jira to see synced components. They don’t overwrite Jira components, but duplicates can happen if the naming isn’t consistent. Treat Compass as the source of truth and avoid creating components manually in Jira. For better tracking, Backstage could help, it has a free tier and works well with Compass.

Cate DiNoto

Yes, the issue is due to a couple of contributing factors. Thank you for confirming that the historical Jira components the team created will not be overwritten by Compass components when enabled in project settings. The team is in the process of shifting from straight up Jira only use, to using Compass as the source of truth for apps & services in our portfolio.

I will check out Backstage to see if we can leverage that.

I went to the Jira Product Discovery demo on 4Mar. It appears to be a paid add on and not yet convinced it would be a good fit for the team. What do you think of this product? Pro/cons?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud