You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have set up a workflow with an approval step in JSM Cloud and am struggling with configuring the transitions to Approved or Declined to function in the way my stakeholders want.
In both the Customer Portal and the internal JSM view of an approval step, I can't require an approver to add a comment for either transition. I added validators to both transitions in my status workflow but it does not work - it just moves to the next status based on the approval decision without requiring a comment (and in the case of a Declined approval, without requiring a resolution).
I am stumped as to why I can't enforce this. What am I missing?
This is expected behavior, the approval process overrides any validators that you have on the workflow for those transitions. Based on this suggestion, JSDCLOUD-6988, Atlassian is adding new feature request to add a comment as part of the approval.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.