It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
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?
"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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was going to just +1 about having the same problems.
But since the page is prompting with "Suggest an answer" . . .
Asana ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.