The Approve/reject choice shows up in Comments for finishing Authoring. This is different from 5.2 behavior. Deliberate change or bug?
@28738
It's a bug, *I think*. I am confused about the approval element of the dialog. In the old CMS UI, only tasks of the CMSTask.APPROVE type got the approval element. Based on the other ticket we're discussing, 86411, I'm guessing that the purpose of the approval element is to offer to reenable the prior task, for example to throw it back to the editor for revision. (That BTW, opens up another issue: an approval task may have n required precursor tasks. Do I reenable all of them? CMS and workflow need use cases.)
I agree. We need better use cases & requirements for this behavior. Given that we don't have them, and that it's late in the development cycle, I think the best solution is to make it behave as close as possible to CMS 5.2. For the next release, we should then focus on really analyzing what CMS should do & why.
Fixed in perforce change 29258.