We're currently using Git flow on Azure Devops in the usual setup with master, development, and release-xx branches with their respective feature and hotfix branches.
Every week a new RC gets branched of development, is designated release-xx with an incrementing number and is deployed automatically on the test environment via AZ devops.
When this RC is validated and good to go for production, its merged via a PR to master. After the merge to master, master once again is merged into the new RC, development etc. master goes on to be deployed on the production environment.
This seems to work fine, however DevOps attaches an increasing amount of work-items in every production release. So the work-items that are already deployed in production are attached again, while they have not being linked in new commits or PR's. This process repeats itself, so the amount of user stories is every increasing...
Thoughts about this? Are we merging incorrectly? Am I missing some step in the process? Thanks in advance .
