-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.1.2
-
Severity 3 - Minor
-
1
Issue Summary
Automation rule fails if the user is deactivated after the automation has already been created.
This is reproducible on Data Center: Yes
Steps to Reproduce
- Create a multi-user picker custom field and associate it with project
- Go to Project settings -> Project Automation
- Create an automation rule for the trigger "Issue created"
- Add any condition, let's say Customer Request type is Get IT Help
- Set action on "Edit issue fields" and add users to the multi-user picker custom field as below
- If you create any request from the customer portal then it works fine as below
- Now, deactivate any user which is added to the custom field
Expected Results
Automation rule should add the active users and exclude the inactive user.
Actual Results
- Automation rule fails and multi-user picker is not added to the issue created
- Error in Audit log
User '<SOME_USERNAME>' is not valid for this user picker. (customfield_XXXXX)
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- links to
[JIRAAUTOSERVER-589] Automation rule fails with the error "User is not valid for this user picker" if the user is deactivated after the automation has already been created
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
| UIS | Original: 0 | New: 1 |
| Summary | Original: Automation rule fails if the user is deactivated after the automation has already been created | New: Automation rule fails with the error "User is not valid for this user picker" if the user is deactivated after the automation has already been created |
| Description |
Original:
h3. Issue Summary
Automation rule fails if the user is deactivated after the automation has already been created. {*}This is reproducible on Data Center{*}: Yes h3. Steps to Reproduce * Create a multi-user picker custom field and associate it with project * Go to Project settings -> Project Automation * Create an automation rule for the trigger "Issue created" * Add any condition, let's say Customer Request type is Get IT Help * Set action on "Edit issue fields" and add users to the multi-user picker custom field as below !image-2023-01-31-17-45-54-455.png|width=719,height=288! * If you create any request from the customer portal then it works fine as below !image-2023-01-31-17-48-11-335.png|width=493,height=197! * Now, deactivate any user which is added to the custom field h3. Expected Results Automation rule should add the active users and exclude the inactive user. h3. Actual Results - Automation rule fails and multi-user picker is not added to the issue created !image-2023-01-31-17-52-15-587.png|width=552,height=204! - Error in Audit log {code} {code} !image-2023-01-31-17-52-54-515.png|width=592,height=92! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
Automation rule fails if the user is deactivated after the automation has already been created. {*}This is reproducible on Data Center{*}: Yes h3. Steps to Reproduce * Create a multi-user picker custom field and associate it with project * Go to Project settings -> Project Automation * Create an automation rule for the trigger "Issue created" * Add any condition, let's say Customer Request type is Get IT Help * Set action on "Edit issue fields" and add users to the multi-user picker custom field as below !image-2023-01-31-17-45-54-455.png|width=719,height=288! * If you create any request from the customer portal then it works fine as below !image-2023-01-31-17-48-11-335.png|width=493,height=197! * Now, deactivate any user which is added to the custom field h3. Expected Results Automation rule should add the active users and exclude the inactive user. h3. Actual Results - Automation rule fails and multi-user picker is not added to the issue created !image-2023-01-31-17-52-15-587.png|width=552,height=204! - Error in Audit log {code} User '<SOME_USERNAME>' is not valid for this user picker. (customfield_XXXXX) {code} !image-2023-01-31-17-52-54-515.png|width=592,height=92! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
| Description |
Original:
h3. Issue Summary
Automation rule fails if the user is deactivated after the automation has already been created. {*}This is reproducible on Data Center{*}: Yes h3. Steps to Reproduce * Create a multi-user picker custom field and associate it with project * Go to Project settings -> Project Automation * Create an automation rule for the trigger "Issue created" * Add any condition, let's say Customer Request type is Get IT Help * Set action on "Edit issue fields" and add users to the multi-user picker custom field as below !image-2023-01-31-17-45-54-455.png|width=719,height=288! * If you create any request from the customer portal then it works fine as below !image-2023-01-31-17-48-11-335.png|width=493,height=197! * Now, deactivate any user which is added to the custom field h3. Expected Results Automation rule should add the active users and exclude the inactive user. h3. Actual Results Automation rule fails and multi-user picker is not added to the issue created !image-2023-01-31-17-52-15-587.png|width=552,height=204! Error in Audit log !image-2023-01-31-17-52-54-515.png|width=592,height=92! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
Automation rule fails if the user is deactivated after the automation has already been created. {*}This is reproducible on Data Center{*}: Yes h3. Steps to Reproduce * Create a multi-user picker custom field and associate it with project * Go to Project settings -> Project Automation * Create an automation rule for the trigger "Issue created" * Add any condition, let's say Customer Request type is Get IT Help * Set action on "Edit issue fields" and add users to the multi-user picker custom field as below !image-2023-01-31-17-45-54-455.png|width=719,height=288! * If you create any request from the customer portal then it works fine as below !image-2023-01-31-17-48-11-335.png|width=493,height=197! * Now, deactivate any user which is added to the custom field h3. Expected Results Automation rule should add the active users and exclude the inactive user. h3. Actual Results - Automation rule fails and multi-user picker is not added to the issue created !image-2023-01-31-17-52-15-587.png|width=552,height=204! - Error in Audit log {code} {code} !image-2023-01-31-17-52-54-515.png|width=592,height=92! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
| Labels | Original: iq-a4j | New: iq-a4j ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 956556 ] |
| UIS | New: 0 |
| Labels | New: iq-a4j |