Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,749
Community Members
 
Community Events
176
Community Groups

How to remove auto-detected PR from ticket

Hi,

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

2 answers

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 Atlassian Team Oct 12, 2022

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.

0 votes
Andy Heinzer Atlassian Team Dec 28, 2021

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

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 Atlassian Team Jun 08, 2022

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events