Moving Aha! records to a new workspace broke the link to Jira issues

Coming soon: We are introducing a fresh new look for record drawer and details pages on September 30, 2020. This article describes the current experience. Preview the upcoming improvements in your account now so you can get familiar with the new way of working in Aha!

  • Switch to the new experience using a toggle in the More options button in the drawer of each record.
  • The toggle is unique to each user — so you can opt in and out as often as you like.
  • We also updated the application font in the new experience for improved text legibility.

The integration between Aha! and Jira is between an Aha! workspace and a Jira project. Even if you have all of your Aha! workspaces set up to integrate with projects in Jira, moving Aha! records to another workspace will break the integration link, and if you try to re-send records after moving them, you risk creating duplicate records in Jira.

If you want to move Aha! records, you can, but you might need to do some manual work to maintain that integration link. You have three options:

  1. Relink each feature manually (not available for requirements).
  2. Delete the Jira issues and send the Aha! features over to Jira again to recreate the link to new issues.
  3. Delete the Aha! features and import the issues from Jira to Aha! to recreate the link to new features. 

Option 1 maintains all data in both systems, but is manual and best suited for a small volume of features. You can link them in the Send menu for each feature. This will not link requirements. 

Option 2 will allow you to recreate the issues in Jira in the correct versions with the click of a button. This is the easiest approach. 

Option 3 requires multiple imports from Jira so that you end up with features grouped in the correct releases. If the features are currently being developed and it's important for developers to see all of the commenting back and forth, you may wish to keep the Jira issues and reimport them. 

Note: Since features can contain requirements, these instructions apply to requirements as well.  

Option 2 - Keeping Aha! features and resending to Jira

  1. Move all of your features to the new workspace. This will break the link from Aha! features to Jira issues. 
  2. Ensure there's an integration set up between the new workspace and the Jira project of choice.
  3. Send all of your features from Aha! to Jira. This will create new issues in Jira.
  4. After checking they have been created as desired, delete or archive the old issues in Jira.

Option 3 - Keeping Jira issues and importing from Jira

  1. Create your new workspace in Aha! if it's not created already. 
  2. Ensure there is an integration between the Aha! workspace and Jira project.
  3. Move all of your issues in Jira to that new project (if necessary). 
  4. Import those issues from Jira into Aha! This process will create new features and requirements in Aha! 
  5. After checking the new Aha! features and requirements have been created as desired, delete the old features. If you want to "archive" them, you may bulk edit them to mark all as "will not implement", move them to a release and ship them so they are hidden. 

Was this article helpful?
1 out of 2 found this helpful