RELATED IDEAS
Moving integrated Jira records to a new project should update the Jira link and key in Aha!
What is the challenge? |
When following the guidance in this help article to move Jira records between Jira projects with Jira, https://support.aha.io/aha-roadmaps/integrations/integration-guides/move-records-with-jira-or-rally~7444656710918981281#prerequisites, the integration link and jira key displayed are not automatically updated, even though the link takes you to the new Jira record |
What is the impact? |
Confusion for Aha! users for which Jira project/key an Aha! record is linked to |
Describe your idea |
Ensure that any Jira record that is moved to a new project, when I meet the prerequisites in the help article, are automatically updated in Aha! with the correct display link and Jira key |
© 2025 Aha! Labs Inc.•All rights reserved
The problem I have is with the requirement that it has to match the template exactly. This is especially a problem wrt Status's. The workflow in one Jira project may not match the exact workflow in another Jira project so to be constrained by that requirement is a problem.
The good thing is if record ID changes from ID1 to ID2 across projects, the aha record shows old ID1 but if I generate a report (List), and have the Jira key as a column it correctly shows ID2