-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Integration - Github - Marketplace
-
6
-
Severity 3 - Minor
-
13
Issue Summary
When two separate Jira sites have the same project key and share the same GitHub organization, the Github for Jira app is syncing smart commits from both repositories to both projects on both Jira sites. This causes confusion between the teams as the commits are appearing in both Jira projects. It seems there is no current way to support multiple Jira instances and handle the possibility of duplicate project keys being created in both instances.
It is also worth mentioning that updating the project key will not resolve this issue because the old project key will redirect to the new one. A permanent fix is requested to prevent this from happening in the future, as it may be challenging to coordinate between two different instances to ensure that two projects with the same key are not accidentally created.
At this time, when this happens, there doesn't appear to be a straight forward way to "untangle" the smart commits between these two projects.
Steps to Reproduce
- Create two separate Jira instances.
- In each instance, create a project with the same project key.
- Use smart commits to include the project key in the commit messages.
Expected Results
Ideally, there should be a mechanism to support multiple Jira instances and handle the possibility of duplicate project keys, possibly by filtering repositories.
Actual Results
The smart commits are appearing in both Jira projects, despite them being on separate instances.
- is related to
-
JRACLOUD-99914 Support repository-level scoping and isolation across multiple Jira Cloud sites connected to the same GitHub organization
- Gathering Interest