How to set creator of issue as the "auditor (a custom field)" of your issue in jira automation

[Wendy Chen]

Rule background:

• When an epic is created, it will create 5 stories linked back to that epic.

Goal:

• I want the creator of the epic to be automatically assigned as the "Auditor" of the epic, and the Auditor of the stories that the automation will create. 
• Auditor is a custom field

How can I accomplish this?

Thank you so much! 

[Walter Buggenhout]

Hi @Wendy Chen,

You should be able to create a variable (e.g. {{auditor}}, fill that with a smart value from the epic's reporter ({{issue.reporter.displayName}}) and then use the variable to set the auditor custom field of your linked issues while you are creating them.

Hope this helps!

[Wendy Chen]

So in the automation rule structure, would I include a New Action after the epic is created, select Edit issues field, choose the Auditor field, and input ({{issue.reporter.displayName}}). 

And then in blocks that create the stories, select Audit field to be filled, and copy from the Epic?

[Walter Buggenhout]

Not exactly, @Wendy Chen.

I was thinking you 'd have an automation rule that responds to the issue created trigger, checks if the issue created is an epic and after that condition:

new action: set variable (name: {{auditor}}, value {{{{issue.reporter.displayName}}}}

And then, when you create the 5 issues in that epic, use the {{auditor}} variable to set the Audit field of the issues. 

[Wendy Chen]

Is this how I set the variable up? The second image is trying to edit the Auditor field of the epic issue that is created. 

However, I ran this rule and the error said "

Create issue

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -

Auditor (customfield_28180)"

[Walter Buggenhout]

Hi @Wendy Chen,

Yes. As the error message says: check your field configuration. The auditor custom field must be on the create screen of the issue (type) you are trying to manipulate. Otherwise it can't be filled out.

[Wendy Chen]

Would I change it to this?

[Walter Buggenhout]

No, you must ensure that the auditor custom field is present on the create issue screen in the project where you want to create your issues (or on the edit screen if you are trying to edit existing issues).

Navigate to the project where you are trying to create issues, navigate to project settings > screens, locate the screen scheme used for the issue type you need and make sure the custom field is on the create screen.

[Wendy Chen]

This question that was asked by someone else represents what I wanted to do:

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Automation-for-JIRA-Set-Custom-User-Picker-Field-by-user-who/qaq-p/1259148 

The auditor custom field is not a textfield and is a user-picker-field. I still wasn't able to figure out how to assign the reporter as the auditor, and the audit log kept saying "Fields ignored - Auditor (customfield_28180)". The auditor field is on the create screen of the issue I'm trying to create, so I'm not sure what is wrong. 

[Bill Sheboy]

Hi @Wendy Chen 

To do that, please use the accountId as referenced in that linked post.  For example, when editing the auditor field you may type in this smart value, it will appear below the field, and then you can select it:

{{issue.reporter.accountId}}

If you want it from the trigger issue instead, and I believe you do for your rule, instead please try:

{{triggerIssue.reporter.accountId}}

Kind regards,
Bill

[Wendy Chen]

When I'm editing the auditor field, the Auditor (textfield) and Auditor (userpicker) options appear. The userpicker does not let me input my smart value, and has pre-determined options to select from (i.e. copy from parent issue, epic issue, etc). Since the auditor field is not a textfield on my screen, inputing the smart value in the Auditor (textfield) option doesn't work either. 

[Bill Sheboy]

Did you try what I suggested for the user picker field for the edit action:

• type in your smart value
• the smart value will appear below the field
• select that value below the field
• it will now be used to populate the field for the edit

[jun lee]

Hi

In my case, I am trying to update value to a number field. Can you advice for me?

JIRA Agent user has a administrator role, and the custom field is in a field configuration scheme of this project and screen of this issue type. 

[Bill Sheboy]

Hi @jun lee 

Have you confirmed the smart value for your field to use in the JSON advanced edit?  Please note that the smart value may not exactly match the name of the field on the screen or what is shown in drop-down lists.

You can find and confirm the smart values for supported fields using this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

[jun lee]

Hi

The custom field has not smart value. I can find just name of the filed as 

"customfield_13500":"ENM_WorkPercent"

from xxx/jira/rest/api/2/issue/ENMCOMM-340?expand=names.

As I mentioned before, it is a number field.  Is number field has smart value, too?

[Bill Sheboy]

Based on what you show, the custom fieldname or ID will work as a supported smart value.  Please try using this example to set a number field with your JSON expression:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Number-custom-field

[jun lee]

It sill doesn't work.

[Bill Sheboy]

Is your field defined on the edit view?  When it is not present a field cannot be edited by a rule.

Who is the rule actor (i.e. user) in the details section of the rule?  Has this been changed from the default of "Automation for Jira"?

[jun lee]

the field defined on create, and edit screen. Actor is Jira agent has an administrator role.

[Bill Sheboy]

You seem to have covered all of the things I know which could cause this symptom. 

At this point I recommend working with your Site Admin to submit a ticket to Atlassian Support for assistance.  If you are using a paid license for Jira the admin can do that here: https://support.atlassian.com/contact/#/