Hello, We have a rule triggered by an incoming webhook which creates a ticket and if the reporter user (comes in a custom field in the webhook) does not exists it creates it and should set him as the reporter. The problem is at this last step, the user gets created but in inactive state which causes to fail the step for setting it as the Issue Reporter. Although the "Edit issue" action shows "Issue edited successfully", the Reporter field is not populated with the created user, instead we get "Anonymous" in that field. The weird thing is, we can access the issue and set the created user as a reporter if done by hand, but not in automation. But we need it to be set automatically. Thanks in advance for your help.

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; } } }

Jira automation - Can't create and assign a user as a reporter due to being inactive

Javier Eduardo Marín Fernández

Hello,

We have a rule triggered by an incoming webhook which creates a ticket and if the reporter user (comes in a custom field in the webhook) does not exists it creates it and should set him as the reporter.
The problem is at this last step, the user gets created but in inactive state which causes to fail the step for setting it as the Issue Reporter.

Captura desde 2023-07-27 12-11-49.png

Although the "Edit issue" action shows "Issue edited successfully", the Reporter field is not populated with the created user, instead we get "Anonymous" in that field.

The weird thing is, we can access the issue and set the created user as a reporter if done by hand, but not in automation. But we need it to be set automatically.

Thanks in advance for your help.

Accepted answers

Marc -Devoteam-

Hi @Javier Eduardo Marín Fernández and @Jack Brickey

I think the webhook call triggers the create user action.

As I see this is a new request in a JSM project the created user should be a "Customer" in JSM terminology

Am I correct on my assumption @Javier Eduardo Marín Fernández ?

I think due to the settings in Atlassian Administration, the user doesn't get license (so inactive). This is a good thing, otherwise the user would probably be granted a JSM license.

I found this in the Webhook documentation, in the section: Executing a webhook:

The user includes an accountType field that is used to distinguish different types of users, such as normal users (atlassian), app users (app), and Jira Service Management customers (customer).

Might it be related to this?

All comments

Jack Brickey

Hi @Javier Eduardo Marín Fernández , welcome to the Community.

I have never attempted this but wonder if it is a a timing issue. I see you have re-fetch already in there. As a test, it would be interesting to see if setting the Reporter in a secondary rule would succeed.

Jack Brickey

Also, could you share the specifics for the last component where you are setting the reporter?

Javier Eduardo Marín Fernández

Hello @Jack Brickey

Thanks for your prompt reply. The last action would be set the field "Reporter" as the email of the created user, using the custom field from the payload of the incoming webhook as a smart value:
{{webhookData.customer.email}}

Jack Brickey

Can you add an audit log to inspect that smartvalue?

Marc -Devoteam-

Hi @Javier Eduardo Marín Fernández and @Jack Brickey

I think the webhook call triggers the create user action.

As I see this is a new request in a JSM project the created user should be a "Customer" in JSM terminology

Am I correct on my assumption @Javier Eduardo Marín Fernández ?

I think due to the settings in Atlassian Administration, the user doesn't get license (so inactive). This is a good thing, otherwise the user would probably be granted a JSM license.

I found this in the Webhook documentation, in the section: Executing a webhook:

The user includes an accountType field that is used to distinguish different types of users, such as normal users (atlassian), app users (app), and Jira Service Management customers (customer).