How to unlink a bitbucket branch from the JIRA task.

[Stephen Collins]

I created a release branch from a master branch and for some reason a jira issue is associated to the release branch. The JIRA issue isn't associated to the master branch, but some how there's a JIRA issue linked to my release branch. How can I unlink these two? I'd like to not delete the JIRA task but I will if it is the only way to unlink. There's got to be another way, right?

[Mike Loux]

"Suggest an answer".  Haha, that's cute.  No, I'm chiming in as well.  Same problem, but with a Service Desk Issue instead of a task.  Accidentally created the branch on the wrong repo (because I'm an idiot) and didn't realize it until it was added.  Deleted the existing wrong branch, created it against the correct repo, and now I have 2 branches associated with the issue, and no way to remove them.  And that sucks.  

[dtlhlbs]

https://jira.atlassian.com/browse/JSWCLOUD-21855

[Francesco Salvi]

lol is this seriously 4 yo and still unsolved?

[Jan Pozivil]

Please, tell me this is now possible. I mean 4 years, this is 4 years old. 😱

[Gautam Rai]

I had accidentally created a brach to a different repo, and now no way to remove this unwanted branch to task.

#JIRA should fix it, and provide a way to handle this type of issues.

[Ken_Dellinger]

I was going to just +1 about having the same problems.

But since the page is prompting with "Suggest an answer" . . .

Asana ?

[John Busciglio]

Unable see an intuitive, clear cut, easy way to do this.  The other way this issue manifest itself is that looking at a repository in bitbucket, I don't see a clear cut, intuitive easy way to know what issues are linked to a particular branch.  On top of that, if I want to get back to the place that I initiated the branch creation from, i have to use browser back button.  

Is there some additional options I can add to make this essential element of linking tasks to repo branches work in a less clunky way?  Thanks!

[Chris]

Seems straight forward to have an exception syntax where 'ABC-123' patterns are NOT parsed and interpreted as JIRA task ids.  Perhaps, "{ABC-123}", where the curly braces provide the parsing exception.  They would exist in the plain text entry only, then hidden on rendered view, similar to URLs.

[Amir Ali Tabandeh]

following!

[Monica_Rossetti]

Looking for an answer...I only found people with the same problem and no solution :(

[Dominic Giger]

Well, at least you're in good company. ;)

[Artur Malak]

[*]

[Ricardo Patino]

x2

[john]

I would also like this fixed. FYI, this bug ticket exists.

[Matthias Fleschütz]

Me too...

[Maxim Hébert-Gareau]

I'd really like to remove those unwanted link to non-existent branch too.

[Fabio Ribeiro]

I have the same scenario. I should ask @Mike Loux to have it fixed.

: )

[Mike Loux]

Hah.

[Andrew Murdoch]

+1 on this issue.

This page (https://confluence.atlassian.com/adminjiraserver/synchronize-an-account-938846897.html) looks like it might provide help to clean and "sync" the Bitbucket and Jira applications, but so far (with a "full sync") there is no change to the broken branch links in Jira (where Bitbucket Git branches no longer exist).

[Jobin Kuruvilla [Adaptavist]]

A JIRA issue is associated with a branch if it has the issue key in the branch name. Is that the case here? The only way is to rename the branch.

[John Busciglio]

I deleted a branch that was created from the issue but the issue still thinks it has a branch tied to it.  How to get rid of the association? 

[Deleted user]

I have exact same scenario.

I was testing out how branch creation worked via jira interface

it created a linked branch in my repo as configured during creation

I then deleted the untouched branch from bitbucket.

I want to remove the dead-end link from the jira issue but I cant edit that.

[Deleted user]

Just chiming in to say that I'm having the exact same situation. It would be really nice if there was "un-link" functionality from the Jira Software side (Jira Cloud user here).