Issue Summary

The automation rule attempts to add a user account directly who is already listed as the reporter in the ticket, this will fail with the expected warning message "Reporter was removed from request participants, due to a Jira Service Management API restriction", as demonstrated in the video below:

• Screen Recording 2024-04-04 at 12.25.04.mov

Steps to Reproduce

1. Create a rule
2. Add an edit issue action
3. Edit the request type field adding the reporter

Expected Results

Currently is possible to add the reporter as request participant by:

• Manually adding the Reporter in the Request participant field
• Using the "Advanced edit" action using the JSON below:

  {
      "fields": {
          "Request participant": [
              {
                  "accountId": "{{triggerIssue.Reporter.accountId}}"
              }
          ]
      }
  }

• By using the the web request method Add request participants
• Lastly, another option involves utilizing the "Copy from" action and selecting the Reporter in the "Field to copy value from".

Actual Results

It should be possible to add the reporter as a request participant, but instead, the automation will fail with the message below:

"Reporter was removed from request participants, due to a Jira Service Management API restriction"

Workaround

Change the reporter to another user and then transfer the old reporter to the Request participant field, since by design the Reporter cannot be added as a Request participant, as the Reporter should get the same Email Notifications (duplicate notifications). Thus, this can be archived by using a "Re-fetch issue data" between the edit actions.