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

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 8.1.2
    • Component/s: Configuration, Fields
    • Severity 3 - Minor
    • 2

      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

            Assignee:
            Natalia Wroblewska
            Reporter:
            Aniket Ranjan
            Votes:
            8 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated: