First of all welcome to the Octopus Forums!
Thanks for reaching out.
Does every release have its own version of every package in it? The way Octopus gets its Build Information like commits and Jira Work items is from the build information tab. When you compare the build information for the version of the package that is in the old release vs the newest release, are the work items the same, or different? Can you please send screenshots via DM that show the build information for the package in question for the 2 releases, as well as the release page showing the specific Work Item you don’t want to be in the release?
Typical behavior will eliminate changes an environment has already seen, however, if the build information for that version of the package has the Work item, it will update Jira, even if it has already seen that Work Item in a previous release for that environment.
Here is expected behavior.
In my scenario, I have deployed 1.0.98 and 1.0.99 to Dev, but nothing to Test. When I deploy 1.0.99 to Test, you will see it shows all of the roll-up changes from the last version it has seen, whereas when I deployed 1.0.99 to Dev, you only see the changes for that specific version, because Dev has seen the changes from 1.0.98.
Build Info for 1.0.98:
Build Info for 1.0.99:
Please let me know what you think.