I did a git rebase on pushed history of a repository. This repository is linked to a JIRA project. I know it's a bad idea to rebase pushed history. However I wanted to experience myself why exactly it's a bad idea. And now I have this problem. Don't say: "I told you so!"... :-)
A task shows two invalid commits in the Agile board. That's because these commits have been squashed and don't exist anymore. When I click on the link "View full commit", I land on a 404 page on Bitbucket.
How can I remove these commits from the Agile board or refresh the history?
To fix this, you'll need to completely remove the Bitbucket account from JIRA, wait a little while for the database to clear out all the related data, then re-add Bitbucket. When you re-add, it will do a fresh search of the repository and add the commits as they stand now. Your smart-commits will not be reprocessed. This may take a long time if you have numerous or a very large repository.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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