In our production environment, there is a integration between STASH and JIRA. When a user wants to commit source code, he has to mandatorily enter a JIRA ticket so that the source files committed will be captured in source tab of a JIRA ticket. This is enforced through a plugin in STASH.
If a user enters a wrong JIRA ticket during commit, source details gets captured in a wrong JIRA ticket. From GIT perspective, the wrong JIRA ticket can be corrected. However, How to unlink the source details captured in a wrong JIRA ticket? Please advise.
Let me know you need any further details from my end.
When you rebase to fix the issue keys in the commit messages, git merely creates new commits, the old ones are only removed when git does a garbage-collection and prunes unreferenced commits.
Stash manages garbage collection of your git repo (in order to make forks and cross-repo pull-requests work) and is not allowing the pruning of your commits that you presumably rebased to fix the issue key.
So in JIRA, on the incorrect issue, you are seeing links to the old commits (if you click through, you'll probably see that they are not on any branches).
If you look at the correct issue, you'll see links to the corrected commits.
Unfortunately, there is currently no way to force removal of the older commits.
For more information, you can browse various issues about garbage collection in stash https://jira.atlassian.com/issues/?jql=project%20%3D%20STASH%20AND%20text%20~%20%22garbage%20collect%22
Try going to here: https://jira.atlassian.com/issues/?jql=key%20in%20watchedIssues()
then enter this into the search box: project=stash AND text ~'garbage collect'
Or see if this link works better:
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot