I suggest you create a custom field named Reason for Rejection, place it on the transition, and make it required. It will make it easy to display or search on it. You could go further and make it a select list with the acceptable reasons so you can group them together for reports. Using contexts you can vary the select list by issue type or project.
Unfortunately- I work for a larger company and I am not an admin so I wont be able to do anything like that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi taher,
in the reject-transition of your workflow, add a validator "Field Required Validator". Then the issue can't be rejected without adding a comment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.