Initially, I considered using deployment packages to track changes. However, I noticed that once changes are pushed from UAT to Production, the environments become synchronized. As a result, all objects appeared in the deployment package; however, the ones that were initially modified before being pushed to Production are no longer listed as 'modified.' This makes it difficult to track the specific changes made during that deployment.I'm looking for a reliable approach to maintain visibility into code changes with each deployment. Has anyone found a good solution or best practice for this scenario?
Discussion posts and replies are publicly visible
We implement traceability by adding every changed object to user stories, and note user stories in the code where the change happens.
Some store full app exports to a GIT repo.
In the end, it depends on what you want to achieve.