Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Converting Jira work item's components from Jira to Compass

Keith Furnell
Contributor
May 1, 2025

It seems that when Compass components are enabled in Jira, existing work items retain their Jira component (had hoped they might automatically convert to a Compass component of the same name).

Given this, we've explored bulk converting work items' Components field content (painfully, one component at a time), however the available options don't actually seem to support this:

  1. Add to existing -> should work, except without #4 it results in duplicates
  2. Replace all with -> should work, but is not suitable for work items with multiple components assigned
  3. Clear field -> like #2 but worse
  4. Find and remove these -> doesn't work, the drop-down list only includes Compass components, not Jira components (possible bug?)

Has anyone else come up with a solution for this? The best we've come up with so far is to search for items that only have a particularly component (not that easy) and then use #2 - i.e. not touch items with multiple components.

1 answer

1 accepted

1 vote
Answer accepted
Pavel Shkleinik
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 1, 2025
Keith Furnell
Contributor
May 1, 2025

Useful to know (and surprisingly that it is not mentioned in https://support.atlassian.com/jira-software-cloud/docs/switch-between-jira-and-compass-components/)!

When it says "Use this script to migrate your existing project components along with issues the components are used on to Compass", what does the bold part mean (given that a pre-requisite is that the project has been switched to Compass? Just wanting to understand if this script does more than update the components references on issues...

Like Pavel Shkleinik likes this
Keith Furnell
Contributor
May 2, 2025

OK looking at the script I see that it will create new Compass components where there is none matching a Jira component name. That's not the behaviour we're after (we just want to leave such legacy Jira component references alone), but it should be easy enough to adapt the script.

Like Pavel Shkleinik likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events