Usage of Jira Deployments with staging environment

[Ricky]

I have set up Jira deployments to track Github deployments to our staging environment. The staging environment is our only environment pre-prod and is used by our PMs to test stories before they go to production. We only deploy feature branches (not long living branches) to the staging environment.

Currently, the PMs don't have an easy way to find out what is deployed to different servers in the staging environment. I thought that the Jira deployment view might help. However, I suspect that the Jira Deployment view is only made for long living branches. It shows data that I can't make sense of: Branches/tickets that are already merged and deployed to prod will be displayed as deployed again between 1 - 5 times thereafter, making the view incomprehensible at the moment.

I suspect  that it internally creates a diff between the commit SHA of the last and current deployment and associates those commits to tickets and then creates a deployment in the respective tickets.

Can somebody confirm or deny this? Is there a way to make this work for our setup?