In classic release pipelines, the “build info” that gets pushed to Jira (via the Azure DevOps–Jira integration or a connector) is typically:

• Tied to the single build artifact that the release is using, and

• Limited to the commits directly associated with that build.

So when a new deployment happens, Jira only shows the commits for that build, even though operationally, you might be deploying a range of commits since the last time that environment was updated.

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available