jnavin I think that adding

 Workaround

 Currently, there is no workaround.

in the issue would make it visible in https://jira.atlassian.com/browse/JRACLOUD-70206?filter=98153

we would also like this feature

I hit the same issue filed in this ticket. I amended the commit message and inserted the correct ID, but, the old commit stays lingering in the ticket with the message: "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository". A fix to this is much appreciated.

This fix would be very helpful. 

This has caused a lot of headache, please fix 

+1

+1

+1

+1

+1

+1

+1. I think it is own of the most common pains for lots of development teams. 

+1

+1

+1

+1

+1

+1

Actually the situation can also come up when a pull request target branch is changed.  No idea why, but this triggers all commits in between the branches to be linked.  Less than ideal.  

> Based on Atlassian's lead time, this would be available around 2028?

 
Optimistic it will actually get addressed at all aren't you

+1

+1

Please, I just encountered an issue where the branch name is associated with the Jira key and branch name cannot be updated. 

+1

+1

really weird not to have un-link feature, 

+1 to this, it is very annoying not to be able to unlink.

+1, We are having this problem too.

As we are all human, occasionally a mistake is made when entering the Jira ticket number to a commit or PR in GitHub, and so an incorrect association is made. Currently that is a permanent association. This is problematic for audit and traceability reasons.

This means that the Jira tools with GitHub integration cannot be used to comply with ISO (and other) standards, which generally demand traceability for all edits to a software base. All for the sake of what must be a small fix.

Surely it would be easy to add support for directives at the GitHub end, e.g. entering RemovePR:ABC-123 in a PR description will remove the link.

Please look into fixing this issue.

+1. This comes up very often. After removing the errant reference to a ticket number from a PR, it'd really help to have a way to remove the link to that PR from the ticket.

Based on Atlassian's lead time, this would be available around 2028?

Come on guys, this is pretty ridiculous that this basic feature is not available in 2023.

Please! Fat fingers are messing up all automations. 

+1

+1, please allow this.

This would be a good feature to add whenever possible. We all sometimes add a wrong PR to a Jira ticket and need a way to undo our fat-finger mistakes.