nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Possible to manually add a BitBucket commit to JIRA issues?

George Irwin4

I forgot to add the Issue key to a commit message the other day. Is there any way to manually attach/link that commit to the issue in JIRA (as if I had included the issue key in the commit message)?

I know there are ways of changing the commit message through git, but the general rule of thumb is not to do it with commits which have already been pushed......

If this isn't currently possible, it would be a great feature to add!!

Accepted answers

Abdulrazaq Mohammed Ali Omar

If a commit has been already "pushed" then you can't edit it (as far as I know). But JIRA DVCS connector can only sync commits which contains issue keys, but you might consider adding a commit with something like "to sync with JIRA".

All the best.

All comments

Abdulrazaq Mohammed Ali Omar

All the best.

George Irwin4

Thanks Razaq, but my goal is to get the changed code from the earlier commit to appear in the issue's comments. Unless I'm missing something, even if I perform another commit with the issue's key, the relevant code (from the earlier commit) won't appear in the issue as the new commit will not include the old changes....

Had a feeling this wouldn't be possible, but could it be considered as a new feature? It surely shouldn't be too hard to show a list of recent BitBucket commits and then link a commit - and the changed code - with a specific issue in JIRA?

Abdulrazaq Mohammed Ali Omar

Would be great if you can submit a feature request in the DVCS Connector issue tracker. You might need to setup an account before you be able to.

George Irwin4

Doing that now, thanks Razaq.

+1 here as well.

+ 1 too

+1 here as well!

FYI the feature request is https://jira.atlassian.com/browse/DCON-256

daniloprates

old issue, current need

ChangJoon Lee

Please, vote here for this feature.

https://jira.atlassian.com/browse/JSW-14378

blair.gemmer

You can use git to amend commits.

http://stackoverflow.com/questions/1186535/how-to-modify-a-specified-commit-in-git

If you just need to change the message, use this link:

https://help.github.com/articles/changing-a-commit-message/

blair.gemmer

You can use GIT to amend past commits. http://stackoverflow.com/questions/1186535/how-to-modify-a-specified-commit-in-git

If you just need to change the message, use this link:

https://help.github.com/articles/changing-a-commit-message/

Justin Greenwoo

Older messages have to be force pushed - in the link you provided, even, this is what they say,

We strongly discourage force pushing, since this changes the history of your repository. If you force push, people who have already cloned your repository will have to manually fix their local history. For more information, see "Recovering from upstream rebase" in the Git manual.

Aleksei Kozadaev

What Justin Greenwood said! If you screw the repo you can recover it with reflog, etc (not easy but possible), but you still can end up with bitbucket's view on the world is different from your local git repo. So really force-push is evil as it is and besides bitbucket is not always great in handling that

rakslice

... and supposing you were in a situation where you could for some reason safely force push the repo without impacting other users, are you saying that the JIRA DVCS connector for Git would 1) even notice the change, 2) update the old JIRA issue to remove the commit, and 3) update the new JIRA issue to add the commit?

Matias Goncalves

When it happen to me, I add a link to the commit as a new comment in the Jira issue. I know it is not the best solution but I have linked the Jira issue with their corresponding commit....

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

bitbucket-cloud

integration

commit