You don't mention it here, but I'm going to guess that you're talking about a git repo. That Stack Overflow answer is talking about a Mercurial repository, and Mercurial is the only one of the two systems that has the "strip" function.
For git, you'll need to remove the bad commit(s) locally, then force-push your revised branch(es). http://stackoverflow.com/a/1338744/5054717 discusses some of that approach, but be warned that you're probably going to break things for anybody else who uses the repo.
One gotcha, Jira counts the commits that are tagged with a given issue ID.
When you force-push new commits *replacing* the old ones, it still counts the old ones even though they're inaccessible without knowing the commit ID (and are not wanted).
In my case, I was taking a feature branch (git flow) having finalised the functionality, and squashing about 150 commits down to about 50. After I was done, Jira reported about 250 commits when Bitbucket's branch viewer showed there was much less.
Thus, the commits still hang around like an unwanted bat colony in cases where you have Jira cloud linked with Bitbucket cloud.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
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