How to remove auto-detected PR from ticket

[Ryota Hashimoto]

Hi,

Any ideas on how to remove the reference to a PR that has no relation to the ticket, automatically detected though?

[Murali Krishna Chevuri]

In my case, I mistakenly created the branch using the EPIC ID. Because of this, I am not able to close the EPIC.

I fixed the issue using the cloning option.

1. Cloned the EPIC.

2. Moved all the child tickets to the new cloned EPIC.

3. Closed the main EPIC by choosing the Duplicate option.

[Amir Ali Tabandeh]

So looks like another method used for the auto-detect, is reading comments under the jira ticket? 

How can we remove that?

Also, slightly related thread here 

https://community.atlassian.com/t5/Jira-questions/How-to-unlink-a-bitbucket-branch-from-the-JIRA-task/qaq-p/712305#U2159752

[Andy Heinzer]

Short of unlinking the entire repo from within Jira, you can't do this from Jira's side.  Instead I'd recommend going to the source of the pull request/commit/branch and trying to make the change there.  This would typically be Bitbucket, Github, or whatever tool you use to track development work.

We have a feature request that seeks to improve this behavior from Jira's side over in JSWCLOUD-21855.

[Andy Heinzer]

Hi Ryota,

I understand that you have a pull request appearing on a Jira issue that is not related to that issue.  Jira is only able to make such pull requests appear on a Jira issue when the Jira issuekey appears in the pull request title or comment.

If you can edit the pull request to change and remove that Jira issuekey from it, then yes you can get Jira to remove this kind of link.  However there is no other feasible way to remove this manually from Jira.  Jira isn't manually creating any such links, all of these for pull requests, commits, branches, etc are automatically creating these links only when the development tool (such as github, bitbucket, etc) includes the issuekey.  More details on how this works can be found over in Reference issues in your development work.

If this is not your own pull request, then you might need to reach out to the author of that PR or an admin of your github/bitbucket repo in order to edit that title to remove the issuekey in question.

I hope this helps.

Andy

[Gaurav Aggarwal]

Thanks Andy. 

> If you can edit the pull request to change and remove that Jira issuekey from it, then yes you can get Jira to remove this kind of link.

I have a question about this. A PR included a Jira issuekey by mistake. Typo. This PR got associated with the incorrect Jira issue.

The PR was then amended to include the correct Jira issue. This associated the PR with the correct Jira issue. However the older link to the wrong Jira issue still remained intact.

How can I modify and remove that link manually? Or can I?

[Andy Heinzer]

Hi @Gaurav Aggarwal 

I took a closer look at this with my own Bitbucket and Jira integration.  The problem here is that some elements of the pull request can be amended, such as title or description, but other elements cannot, such as branch name.   At least in my own case, even if I decline this pull request, and then even go as far as delete the branch, this pull request in my example still contains the old issue key and in turn still show on that old issue.

So in some cases, it might not currently be possible to unlink this mistake.  I did come across a feature request that seeks to improve this behavior over in JSWCLOUD-21855.

[Jesus Garate]

Dear Andy Henzer,

It happened exactly the same way to me. The only solution I could find is to add a link to the actual in the comment section of the Story...

• The old PR was not able to be merged... so I have deleted the PR and its branch!!!
• The new PR is merged

but the Jira ticket is still pointing to the old deleted PR/Branch   :(