Ensure Commits SHAs changed from a rebase or squash on GitLab are synced/updated/deleted on Jira

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Currently the Jira Development section of the Jira Connect app shows all commits, even though they may be deleted, obsolete, or have had their SHAs changed.

• Commit hashes change every time a rebase is done. The parent changes, there are often conflicts that are fixed, etc., which result in a different SHA.

• When commits are squashed, the commit history is changed and the squashed commits are made 'obsolete'. The links to the commits in Gitlab work - the commits are not deleted - but are obsolete and so shouldn't appear in the Jira Development section of Jira Issues.

Because commits are not properly updated in Jira, the commit view in the Development section is not usable

To replicate this behavior:

• Create a repo
• Connect the Jira plugin
• make branches
• commit and push changes to those branches
• squash commits
• force push to the branches
• create and merge MRs
• look at the results in the Development section of the Jira issue.