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; } } }

How can you link source to an issue after a commit has happened (in GIT)?

Hector Palacios

Is there any way to link a GIT commit to an issue after the commit is already pushed to the remote without having added the issue ID to the commit message?

Notice that a commit that has been pushed to the remote cannot be ammended/editted. I was hoping that adding a comment with the SHA1 of the commit would establish the link between the issue and the commit. Or even if there is a more complex way of doing it. But this is a real need.

A similar question has been posted before (https://answers.atlassian.com/questions/5795), but referred to source code in SVN.

Accepted answers

Chii

Assuming you are usin the JIRA Fisheye Plugin, the only way to link a commit to a JIRA issue is via the JIRA issue key in the commit message. Unless you are able to amend the message (which seems like you can't/won't), then you are stuck.

All comments

Chii

Hector Palacios

Yes, I'm using Fisheye. Has Atlassian considered the possibility of implementing a manual linking of issues and source code in GIT? I think this would be a very good feature.

Thanks

Gary Taylor2

I'd vote for such a feature too.

Stanley Goldman1

The lack of this feature means I also cannot correct incorrectly linked changesets.

Can we be linked to a feature request page where I can vote for this?

Stanley Goldman1

The lack of this feature means I also cannot correct incorrectly linked changesets.

Can we be linked to a feature request page where I can vote for this?

Eli Nunna

Inability to arbitrarily link issues to source code severly limits the usefulness of fisheye integration in jira.

William Roush

Ouch, that's rough. Makes fixing issues impossible and all we need is a simple UI element to do this!

Brady Vidovic

Same problem here!

Midori

Instead of fixing this problem, you may want to prevent this using the Commit Policy Plugin:

Edit Commit Policy.png

You can enforce a strict condition to include issue keys matching a JQL query's result. It does work with Git (plus Mercurial and Subversion).

Edit Commit Policy.png

Susan Blyde

Actually, you can put the SHA into the comment field in the Jira... The person has to know to look into the comment though, but if they do they can jump right to the commit

Welcome!

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

Quick Links

Find more posts tagged with

jira

git

issue-link

source

smart-commit