We have OnDemand JIRA and use BitBucket.
Occasionally, we perform a git rebase to remove incorrect commits. Especially ones that forget to add the issue tag to the commit message.
Because of this, other commits that were modified as part of the rebase show up as duplicates attached to their respective issues.
Eventually, BitBucket prunes the orphaned commits. But JIRA does not remove the links from the issues.
At this point, JIRA has commit links that show up as 404s if you click on them.
Re-indexing does not appear to resolve this.
Is there any other steps we can take to remove this clutter?
You can hard refresh the data stored by the DVCS Connector by visiting Cog (Administration) menu -> Add-ons -> DVCS Accounts. Then Shift+Click the refresh icon next to the repository that has had data rewritten. From the dialog that appears, you can force a complete refresh.
Thank you for this information. Shift+Click was definately not intuitive.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It'd also be nice if JIRA (and Bamboo has this issue too) did this automatically. 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.
I did this, and it half worked.
Now, in the jira dev panel, the commit count still includes the stale commits. when i click the link, i only see the current live commits (so that's an improvement), but underneath them, it says "You don't have access to view all related commits"
Yeah, that's definitely a bug! (ps i am an admin).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@aMarcusThis is not a solution but a workaround. If one's workflow is based on rebases, they'll have to perform full sync over and over again, and it'll never give them the right feeling. Rebases should be dealt with automatically.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with @Mike Gelfand this workaround is inconvenient and for admin users only.
What about to make an option inside the Jira task to refresh commits just for the task? This option should be accessible for all users with edit task rights.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@aMarcus there is no such refresh icon in the current version of JIRA (cloud).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any progress on this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are there any updates on this by Atlassian?
Our users are asking for this option to keep their git references on tickets clean.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sounds like what I need. I amended the last commit and now I have two showing in the commits list for my issue in Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
By the way, I could not work out how to follow the steps in this answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.