How to import Jira Compnents in Compass without lose componets history?

Jesus A. Ortiz Durazo

I have some Dev Teams with some Jira Projects, and they have to many Jira components created, but recently we acquire Atlassian Compass, and we need to move all components to compass, but we don't want to lose the Jira components history because that history brings value when they search the functional traceability, here I have 2 doubts:

1. How can import Jira Components in Compass and is a sure way to do not lose the component's history? (the components can exist in Jira and Compass or only and Compass after move them).

2. What is the best practice to maintain a good Jira Components history and a good Compass relationship to show DevOps metrics? (I was thinking to create the same components in Commpas ising batch/csv adding a prefix llike  "Commpas" or "Cmp")

I would appreciate your comments,
King Regards.

Hitesh Sethiya

Hi @Jesus A. Ortiz Durazo 

 

"How can import Jira Components in Compass and is a sure way to do not lose the component's history? (the components can exist in Jira and Compass or only and Compass after move them)."

Great question! To safely migrate Jira components to Compass without losing history, please follow the steps outlined in our Migrating Jira Components to Compass guide. script

It’s straightforward—just run the commands provided in the guide and enter the required details to ensure you’re accessing the correct site with proper authorization. This process helps maintain data integrity during the migration.

Here’s what you’ll need:

• Your site address (e.g., mycompany.atlassian.net)

• Your email

• An API token -  generate one here

• The project key (available from the Jira project’s settings page)

---

"What is the best practice to maintain a good Jira Components history and a good Compass relationship to show DevOps metrics? (I was thinking to create the same components in Commpas ising batch/csv adding a prefix like 'Commpas' or 'Cmp')"

The best practice is to migrate existing Jira components into Compass and then continue managing them from Compass. This ensures that your component history is preserved and that Compass can provide rich DevOps insights based on those components.

Creating separate prefixed components manually could lead to duplication and fragmented data, so we recommend using the migration flow to keep everything consistent and connected.

Let us know if you’d like help with the setup—we’re happy to assist!