Jira Align connector is creating duplicate issues in Jira Align Self-Hosted instances
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This article aims to solve an issue reported by customers whereby the Jira connector creates duplicate features and stories in Jira Align.
Solution
This duplication of items behavior usually happens in 2 situations:
When there is more than one connector pointing to the same Jira instance.
Please make sure that each connector points to a different Jira URL
In case of multiple servers (like one prod and one DR), verify if there is not an instance of the connector running pointing to the same Jira instance
In the case of more than one web server running the application, pointing to the same database.
In case of more than one web server running the application, make sure only one of the servers is running the connector service.
To facilitate the understanding let's call them Appserver_1 and Appserver_2.
Leave service AgileCraft_Jira_jiraalign_<CUSTOMER_NAME>_1 running on Appserver_1
Stop service AgileCraft_Jira_jiraalign_<CUSTOMER_NAME>_2 from Appserver_2 and set the startup type as manual (this will prevent the connector service starts automatically in case of server restart).
Was this helpful?