Is your feature request related to a problem? Please describe.
I was looking through the workflow documentation and the below image from those docs is exactly what we’d need. However the In Review =Reject=> Changes Requested =Back to Draft=> Draft portion, is there a way in that when rejecting a comment could be required? That way when the writer has something that was in review come back to them they have some context as to why.
Describe the solution you’d like
As part of the workflow setup you could add transition actions such as add comment with options based on the action such as required or optional.
Bonus Points
I’d like to see these transition actions be flexible, if not customizable, so we could potential add more than just a comments
Describe alternatives you’ve considered
I mean there are plenty of other ways to communicate that rejection context but seems like it should be linked to the workflow
Thanks!