when using JSD for internal process, it's good to clarify the reason of decline, but it is missed sometime by the approver, is there a way to force leaving a comment on decline of request?
Hi Dell, welcome to the community!
Are you using a transition when declining a request? If so, you could create a transition screen (Decline) and on that screen populate the decline reason.
Then, you could add a validator to the transition that would require the reason be filled in.
The only limitation here is if they are approving via email and not w/in the app this won't work. Often times w/ JSD the approver doesn't have direct access to JSD, e.g. a CFO approving staffing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jack, any workarounds for situations like those? Some of our approvers are non-license users (SVPs who would prefer e-mail or portal interaction) and we typically "encourage" them to leave comment. So it's a bit manual but I'm just not sure how to enable this at the moment. Perhaps this should be a new feature request for Atlassian?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am Wondering if you came across this kind of requirement and have overturned it with any script or other solution?
https://jira.atlassian.com/browse/JSDSERVER-6450
When there are multiple approvers on an issue, if only one denies or approves, the issue is transitioned without giving other approvers an opportunity to agree or disagree. This results in a lot of administrative work as these issues have to be placed back into a status requiring approval so the approval step can be repeated.
Create a way to configure workflow transitions for approvals based on the number of approvals/rejections. For example, if I have three approvers on an issue, I could set the following for the approval:
In this example, if any one approver gives the green light, the request is approved. If one denies it, however, another will have to agree to deny the request.
This allows my team to more effectively distribute approval responsibility without creating significant administrative overhead.
No workaround at this time.
Thanks and cheers.
Milan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.