Bringing the work your team has completed elsewhere has never been easier. With our Jira importer, your progress, history, insights, and all the wins you’ve made together elsewhere can now be imported directly into Clubhouse.
We’ll work to improve every facet of this import process using your direct feedback and insights along the way. Ready to get started?
Before you begin
Preparing for the import will ensure a smooth process from start to finish. Here are some key things you'll need to complete this process:
- Admin (or Owner) status on Clubhouse (Members cannot see the Import page in Clubhouse)
- Admin status on Jira (used to generate auth keys and tokens)
- Confirmation that your data lives on Jira Cloud - we are unable to support imports from Jira Server at this time
And, while certainly not mandatory, it could be helpful to consider doing these optional steps as well:
- Create a new Project that will house your Jira data once imported - it will be much smoother to create this before the import rather than during
- Create any new Workflow States you might need to match current Workflow States in Jira to save time
- Select Jira from the import options to head to the next page.
- Enter in the email you use to log in to Jira. (This must match your Jira email that has Admin status)
- Enter your generated authorization token. This can be found in Jira: Account Settings -> Security -> Create and Manage API tokens
- Enter in your API hostname. Example: youraccount.atlassian.net (make sure to remove the https:// if you're copying this link over)
- Enter in your Project Key. Learn about the Project Key and where to find it here.
- Select a Project to house your Jira data. You can use the generated one, map to an existing Project, or select a new one that you may have made in the planning portion of this process.
- Receive the "Success!" confirmation that your data is ready to be imported, and hit Next: Map Story Types.
- Map your Jira issue types to Clubhouse issue types (Chore, Bug, or Feature). We'll also apply a Label with the previous Jira issue type to help your team stay organized.
- Verify the data looks correct and hit Next.
Note: Jira Epics will be imported as Clubhouse Epics. Jira Subtasks will be imported as Clubhouse Stories with a dependency on the parent Story from Jira.
- Map your Jira Workflow States to existing Clubhouse Workflow States. You can also add a new Workflow State if needed and return to this process.
- Make sure everything looks great and hit Next.
- Map Jira users to existing Clubhouse users. Note: Jira users that are not mapped to existing Clubhouse users will still retain history activity within your data and can be invited post-import.
You're all set - the hard work is now done! Hit Finish Import and let the importer do the heavy lifting. A screen will appear letting you know the import is now in process, and that it's safe to return to exploring Clubhouse while the importer works in the background.
You'll receive a small pop-up message letting you know that your data has been imported successfully. That's it! You've completed importing your data from Jira.
What's next? You can now directly check out the contents of the Project housing all of your Jira data, or invite any users that weren't mapped during the process.
Your imported data should be easy to identify around Clubhouse by their new Labels. Head to the Labels page and view the newly created Labels that accompany the Jira data. You can also use our bulk Story editor to make large-scale changes on Labled Stories.
Need to roll back this import and try again? That's easy, too! Head back to the Import screen within Clubhouse and navigate to the Past Imports thread. From here, you can delete previous imports
Running a second import will create new stories for Jira tickets that have already imported, resulting in duplicates.
There are a few of options to get those additional tickets into Clubhouse as Stories:
- Create a new Jira project, move the new tickets there, then import just that project (this is the easiest option, but note that these won’t be in the proper project in Jira, if that matters.)
- Rollback the prior import completely and re-import to get the new stories (Note that this will cause any changes done on the Stories that were part of the prior import to be lost)
- Do a new full import into a different project, then move the net new stories to the correct project, followed by a deletion of the remaining duplicates - very manual or would require scripting!
- Create new Stories manually in Clubhouse for the new tickets in Jira