+1

+1
This will be very helpful and needed.

+1

+1

Developers keep merging code before linking the Jira and we have no way to add the relationship of Jira to PR afterwards. Please address this concern.

319ba8c4e46e perhaps this is hiding the main problem that there is no way other than PR titles to link a PR to a Jira issue.

It's been 6 1/2 years since this request was opened. When will it get implemented?

There are genuine end-user use-cases where this solves problems after a pull request was perhaps merged a little too quickly without someone realizing that something as simple as the Jira issue ID not being in the title, so now the Jira integration won't work.

Let's go Atlassian!!!

PS: If there are reasons why certain organizations DON'T want editing to be possible, create a project or repository-based setting for this. ideally as a future option so that the majority of users who DO want this can get it ASAP.

This issue has gathered enough interest to be moved automatically to Reviewing status, where it will be reviewed to someone in the relevant product development team and moved on to the appropriate status.

Seriously...why you can't edit?!?!?! 
And also why sometimes it proposes closing the branch, others it proposes deleting it?
+1

Voted for this.  It's important to be able to change the Jira number on a PR, even after it's been merged.  I'm not sure why validation to prevent this would have been implemented in the first place.

+1

+1

+1

+1

+1

+1

@dparrish This is a much-needed feature. Please prioritise!

Request for comment to Dave Parrish / Atlassian:

What are the metrics that determine whether this issue will be addressed?
Is 172 votes a meaningful number?  Being open for 6 years certainly doesn't look like anyone at Atlassian cares.
The issue seems like it should be a simple fix.

Thanks.

+1

+1

+1

Also would be nice to be able to do this to fix consistency issues.

Also would be nice to be able to do this to fix consistency issues.

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

++

+1

Lots of interest - for both editing the title and description of a closed or merged PR. Nothing like this should ever be "permanently locked in" - must always account for human error and possible security issues, e.g. mentioning something you shouldn't have in the description.

+1

+1

+1

+1

+1 This would be so helpful!
 

+1 this would be a great feature to implement.

Would be very helpful!

+1 this would be so helpful!

+1

+1 voted

+1 voted

+1 voted.

I'd like to edit description also, please!

@c8fa61a3a50b, still have not heard anything from Atlassian team since they changed the status to 'gathering interest'.
 

+1 to this, and is there any response from Atlassian team on this issue?

Pretty sure this issue has created an entire community of ex-Bitbucket users, myself included. xD

Our list of merged PR's is a mess and the only way we have to organize them is by title.
+1 (...plus more features for PR's please, like tagging, at least)

+1

+1

+1 need the same

YES!!! please consider this. We often get PRs and Jira tickets out of sync due to typos or simply branching from the wrong ticket. Branches can be renamed, but PRs are stuck in eternal limbo since they cant be edited!

Attachment 3832664834-2manyPRlinks.png has been added with description: Originally embedded in Bitbucket issue #15190 in site/master

Yea, an engineer transposed a digit in the ticket number in the pull request and now that history shows up in a new ticket that has the typoed number. I.e, this isn’t just a cosmetic issue.

Related issue referenced here: https://community.atlassian.com/t5/Jira-questions/Jira-showing-wrong-Pull-Request-info/qaq-p/757462

Not just title; need to edit PR descriptions, too!

We need this so that we can "unlink" PRs from Jira tickets that were erroneously linked either due to a typo, or even worse when PR descriptions include lists of commits from a merge that then adds a whole bunch of commits/branches/PRs to the Jira ticket. Here's an example the PR list for a ticket that shows 11 PRs but only 1 of those should really be linked to the Jira ticket.

Better if we can avoid this in the first place, but as long as humanz make typoes we reely need a way to repear the pablum!

That would be super useful to have this feature in place.
Once PR is merged - it's impossible to link it to Jira ticket. It's an often case that people simply forget to add right ticket number, especially when PR covers several tickets.

Yeah just realized I mistakenly added the wrong Jira ticket number (I was off by one!) in the title I wish I could fix it :'c

or at least give an admin the rights to do so... just ran into this issue.

I'd like to have that, we'd like to add the jira task in the beginning of title, I can do that before merge, but not after. So I have to click and open pull request page and get the branch name created by jira from there. It's waste of time, and when you have to track many repos to for task deployed it's quite annoying.

Does anyone know if there is an issue open for this?

same here. on several occasions, we've had typos / incorrect issue numbers we didn't notice until after merge, and it would be nice to be able to edit them.

Being able to edit/delete/add the linkage manually would be great.

Sometimes we need to correct the linkage between JIRA and Bitbucket, due to typos, so please give this due consideration.