Hi community,
we have an Escalation Service in place whose job is to post a comment if the issue hasn't been updated in the last 4 weeks to inform the assignee to take actions.
The comment is not posted if on the issue there are inactive users either in custom fields (multi-pickers) or as component lead.
Is there any suggestion to bypass the checks? The goal is simply to add a comment, not to edit the issue so I don't understand why the system is checking the users in the background.
Thanks for your attention and feedback.
Hi @Elena Baldo ,
Would it be possible for you to share the Escalation Service configuration here?
The comment is not posted if on the issue there are inactive users either in custom fields (multi-pickers) or as component lead.
Have you tried to look at the log files if there's anything about this behaviour?
Thanks,
Moga
hi @mogavenasan ,
thanks for reply. We've solved the issue by retaining the existing values with the method
issueInputParameters.setRetainExistingValuesWhenParameterNotProvided(true, true)
In this way the validations performed on any involved users being still active are skipped.
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.
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.