In SF 2023.1, after completing a merge session that had a conflict on a control procedure template, the control procedure of the template that had the conflict will not get the status ‘Ready for review’ from the merge session. This results in developers not knowing which control procedures should be reviewed after a merge.
When a developer manually puts the control procedure on status ‘Ready for review’, the resolved conflict from the merge is marked as a change however.
Expected result: Completing a merge session should put all control procedures of templates with resolved conflict automatically on status ‘Ready for review’. I remember this worked in prior SF versions.
Best answer by Jeroen van den Belt
View original
