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.
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).
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs