Edit "Reporter" field with Automation gives "Inactive User" error even when user is "Active"

XMLWordPrintable

    • Minor

      Issue Summary

      Editing "Reporter" via Automation with Account ID returns "Inactive User" error, however user is "Active"
      This is reproducible on Data Center: no

      Steps to Reproduce

      1. Create Automation as follows:
      • Trigger: Issue Created
      • Action: Create Variable
        • Variable name: matchedEmailAddress
        • Value:
          {{issue.description.match(".*Email: (\S+).*")}}
      • Action: Send Web Request:
        • Method: GET
        • URL: <SITEURL>/rest/api/3/user/search?query=matchedEmailAddress.urlEncode
      • Action: Edit Issue
        • Reporter= 
          {{webresponses.body.accountid}}
      • Now create a ticket that has an email in the description with the following format:
        • Email: email@testing.com

      You will see that the ID pulled is valid and active yet it's being recognized as INACTIVE

      1. As shown below, the user/customer is fully active 

      Expected Results

      • Expectation is that the Automation Recognizes the user as "Active" and correctly assign this user as the reporter.

       

      NOTE: This works for licensed users however when it comes to customers it does not work. Which would be the usual Reporters. 

      Actual Results

      1. As shown below, the user is fully active yet somehow being recognized as Inactive

      Workaround

      None worked at present time

        1. image-2024-05-24-15-22-33-781.png
          image-2024-05-24-15-22-33-781.png
          290 kB
        2. image-2024-05-24-15-23-14-698.png
          image-2024-05-24-15-23-14-698.png
          17 kB
        3. screenshot-1.png
          screenshot-1.png
          196 kB
        4. screenshot-2.png
          screenshot-2.png
          119 kB

            Assignee:
            Unassigned
            Reporter:
            Angel Buendia
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: