How to allow jira to use inactive users on user field?

[Nathan Vinicius Vital Santos]

i've been demanded to temporarily block users on ActiveDirectory under certain criteria. Their users remain on my OU, but appear at JIRA with the suffix "(inactive)". 

However, i have approval-based workflows and process that are getting blocked at creation due to an inactive user being present on the field, even if they're always defined along with someone else.

the goal here is to allow these fields to work and decrease the user's inability to create an issue & the need for the admin's manual intervention to change the field.

I couldn't find a ldap filter to work, any plugin or configuration inside the User Directory to allow these temporarily-disabled-users to not affect their work.

[Marc - Devoteam · Accepted solution]

Hi @Nathan Vinicius Vital Santos 

Check how these users appear as approvers on the issues.

Is the approvers field on creation filled, based on default options set on the request as field approvers is set by default or are automation rules setting the approvers?

Inactive users can't provide actions, as they are not allowed anymore.

As your users are managed and coming from an IDP integration, there is no option to allow the use to be active if disabled on the managed source.

To prevent these user to create requests, you can add request restrictions.

See; https://support.atlassian.com/jira-service-management-cloud/docs/add-or-remove-restrictions-on-request-types/ 

[Nathan Vinicius Vital Santos]

Hi @Marc - Devoteam

These users fields are filled on creation, using a behaviour as they're conditional to what is being required an approval (and they've been required to appear to our users, i couldn't make that happen using only an automation). 

While the Restrictions are already being used, these inactive users won't be opening any requests, i just need them to appear as approvers on these fields and make sure the field won't block the entire creation. 

[Marc - Devoteam]

Hi @Nathan Vinicius Vital Santos 

If these users are inactive they can't approve a request as their account is not active in the instance.

They will need to be active, you could create a separate role in Jira and add this role to the permission scheme and only allow the required permissions to this role, like "browse", "transition"

There is no way around this, as you mange the accounts from the integration with and IDP.

[Marc - Devoteam]

Hi @Nathan Vinicius Vital Santos 

Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request.

This will help other community member trying to solve the same or provide them with a work around

P.S. If the answer is very valuable to you, please share some kudos.

[Nathan Vinicius Vital Santos]

Thank you for your help and informations, @Marc - Devoteam