Summary

Currently, by referencing a Jira ticket in a commit and pushing that commit to Bitbucket, a reference to that commit will automatically show up on that ticket in Jira.

The integration doesn't, however, appear to garbage collect references to dangling commits. These references can crop up very often during the course of normal software development, for example when rebasing, squashing, or cherry-picking in git and pushing to Bitbucket, the "orphaned" commits will still have references in Jira on the associated ticket.

Unfortunately, lack of garbage collection in Jira results in, depending on software workflow, sometimes many (> 10) references to dangling commits on a particular ticket, which reduces the utility of the Jira and GitHub integration. Some mechanism for garbage collection of references on tickets to dangling commits would greatly improve usability. Ideally, this would happen automatically behind the scenes.

Suggestion

Adding the ability to remove commit references automatically or manually on tickets would be helpful, e.g. a garbage can icon next to each commit reference.