Sometimes a situation arises where a team that has an integration with Jira running needs to migrate their server or otherwise update the Jira domain being used in the integration.
This can raise a few concerns on the Aha! end due to the tightness of integration between the two applications.
The first concern is that Aha! stores the URL of the Jira issue. This URL will be different now, so clicking on the link to the issue in the user interface won't work. However, this is purely a cosmetic problem. Aha! uses the URL from the integration configuration when communicating with Jira to perform syncing. So links to existing issues will appear to be broken in the UI, but the issues will continue to sync correctly.
The second concern is a bit more complicated. Aha! stores the unique identifier for each linked Jira issue. This identifier is an integer, and is not normally visible in the Jira UI. The identifier is necessary because it is possible for the issue key (like APP-123) to be changed. Some methods of moving from one Jira instance to another will change these identifiers and so Aha! will no longer be linked to any issues - even though it displays the same key in the user interface.
The issue ID is a somewhat hidden field in Jira. The easiest way to find the ID is to open an issue and mouse over the edit option. The status bar on the bottom of your browser will display the URL with the issue ID.
If the issue ID is going to change, the integration will be broken for any previously linked Aha! record. There are three ways to fix this issue, beginning with the easiest:
- Delete all the previously linked features from Aha! and re-import from Jira.
- Do the opposite, and delete the issues from Jira and re-send everything from Aha!
- If you have a very small number of features and issues, you can also manually link each Aha! feature to a Jira issue under the Send menu in each feature.
Note: This option will manually link only features and not requirements.
For more details on thinking this through see Moving Aha! records to a new workspace did not move Jira issues.
This same process would need to be used if the team wishes to update the reference URLs in Aha! and Jira - although it is a bit of work for what is essentially a cosmetic fix in that situation.
Remember, we do not propagate deletions of data objects so if you delete in Aha! or in Jira the associated object would not delete. This is even more true since the integration link is presumably broken anyway!