Is it ideal when a Ticket or Request or Change is submitted but it is rejected, does it mean you need to submit another ticket or Request or change? just to apply the remarks? what is the best way to this process?
New Idea
Approval Process
+3
+9- Top Contributor ⭐
This doesnt really belong in ideas and is more of a community question but…
My take on the ticket is that when a rejection occurs in an approval process, the ticket should not go through another approval process. This makes things clean from an auditing perspective about who approved, when, etc if it comes up as an artifact for an auditor. Having a ticket re-run through the same approval process can be confusing when looking at the approvals list, comparing against the activities tab, etc.
I’ve leaned into telling managers/system approvers that before they just hit no, if they have questions or things that need clarity to seek them out before rendering a rejection so that an “oops” is avoided due to a lack of information from the approver (or rejector in this case?) and hopefully this reduces duplicate requests.
Join the Community
Already have an account? Login
Welcome back to Freshworks Community
No account yet? Create an account
Social Login
Login for Freshworks Employees Login with LinkedInor sign up below
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.