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.
Smart commits enable your team to transition issues with commit messages. For more, check out this doc: https://confluence.atlassian.com/display/AOD/Enabling+DVCS+smart+commits.
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.