nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Nathan Vital

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.

Accepted answers

Marc -Devoteam-

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/

All comments

Marc -Devoteam-

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 Vital

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"