I am currently testing out the Release Changes feature in v2019.6.7 LTS on-prem.
We have a setup similar to the one pictured in
where every build produces a release, which is auto-deployed to a DEV environment.
However, for all projects, including ones where metadata has been pushed for its packages and JIRA integration / release note generation based on included commits works perfectly, every deployment to subsequent environment (similar to the “1.0.3” deployment in the blog post) will list the single release being deployed, even if multiple releases have been made to DEV in between.
A specific example:
I have a project where releases have been deployed like this:
If I press deploy on release 4.0.21-master-7120239 to DEVTEST i expect Release Changes to list releases 4.0.20-master-8728983 and 4.0.19-master-0722176 as well. Similarly, if I press deploy to AcceptTest, I expect 4.0.20-master-8728983 to be included.
However, both deployment previews list only 4.0.21-master-7120239 in Release Changes:
Am I missing something to make this scenario work?