Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Import data from Clubhouse to Jira Edited

Hi Atlassian team! 

We are using Clubhouse within our organisation, but for obvious reasons, we would like to migrate Jira. Is there any guide on how to map the issue types between the two ?

My current understanding is that we map the issue types as follows:

ClubHouse -> Jira

Milestones -> Epics

Epics -> Stories

(Stories)- Feature -> Feature (custom type issue)

(Stories) - Bugs -> Bugs

(Stories) - Chores -> Tasks

 

Is this mapping correct ?

 

Any help will be greatly appreciated.
Many Thanks :)

1 answer

0 votes
Andy Heinzer Atlassian Team May 07, 2021

Hi Taseer,

While I'm not an expert on how clubhouse organizes issue data, from a review their definition of Epic, it feels to be very much in line with our own concept of what an Epic is.  Which would then lead me to ask, what do they consider a Milestone? In my opinion the equivalent in Jira would be something like an custom hierarchy level in Advanced Roadmaps, such as an Initiative.

That said Advanced Roadmaps is only available in Cloud under our Premium Service plan.  If you are not planning to use the Premium service, then perhaps you could map this issue data differently as you have suggested, but my fear is that some of the relational aspects of this issue data (such as how it relates to other issues) might not be maintained when migrating data between platforms. 

I believe that the other issue types, such as feature, bug, chore/task can all easily be equivalents between platforms. I hope this helps.

Andy

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you