-
Bug
-
Resolution: Unresolved
-
Low
-
3
-
Severity 3 - Minor
-
Issue Summary
When a Bitbucket repository is transferred from one workspace to another, Commits / PRs / Branches & Build Links in the Development panel of related Jira issues do not update to reflect the new workspace. Instead, they continue to point to the old workspace, leading to broken or misdirected links.
Steps to Reproduce
- Create a Bitbucket repository in Workspace A.
- Link the repository to Jira and sync branches/Commits/PRs. For pipeline configurations, trigger a build that is associated with a Jira issue
- The Development panel in Jira shows the Branch/Commit/PR and build link correctly.
- Transfer the repository from Workspace A to Workspace B.
Expected Results
The Branch/Commit/PR and build link in the Jira issue's Development panel should point to the new Workspace B.
Actual Results
The Branch/Commit/PR and Build link in the Jira issue still points to the old repository URL under Workspace A, leading to 404 errors.
Workaround
- Disconnect the integration
- Verify that the development data is removed from work items
- Reconnect the integration to resync
- Contact support if the above steps do not point to the right workspace
- is cloned from
-
JSWCLOUD-18101 System Story Points field is unlocked and can be duplicated
-
- Closed
-
- is related to
-
JRACLOUD-94413 Workflow triggers are reinitiated when existing repository is moved to another workspace and resynced/reconnected back in Jira
-
- Gathering Impact
-
- mentioned in
-
Page Loading...