If I create the work item manually, both assignee and approver fields are on the create screen and I can set their values. My automation rule is triggered on schedule with a JQL. For each matching work item, I create a new work item and copy some fields over. I tried using the COPY option for Assignee and Approvers at first. Summary and Description are copied, but Assignee and Approvers remain blank. Then I tried setting a fixed value as above. Still blank. No error in the audit log, it simply lists the work items created.

Hello @KC Wong Have you made progress on this effort, or figured out your solution? Do you need additional advice? Please let us know. We are happy to try to help!

The JSON you provided shows 7 fields being set during the Create action: * Summary * Description * Project * Issue type * Issue Links * Reporter * [SINO] Vendor The JSON does not support your statement that the Create action is trying to set the Assignee and Approvers fields. Please consider getting multiple screen images and sharing them in order to show the settings of your Create Item action. I don't see anything in the structure of the rule otherwise that would affect the fields being set during the Create action. If you could provide the other information I asked about, that would also enable me to more effectively and efficiently help you debug this scenario. * The rule actor, as I cannot tell from the ID in the JSON if the actor is Automation for Jira. * Confirmation that the rule actor has access to set the specified fields in the specified project.* Related to this, are you working with a Team-managed or Company-managed project? And can you confirm that it is a Service project? You did post in the JSM forum, but sometimes people post in the wrong forum. * A copy of the rule with the Assignee and Approvers fields being set in the Create action * A copy of the output in the rule execution log for an instance when the rule, with the settings for setting those fields, has been executed. Thank you for helping me to help you.

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

Automation rule "Create Work Item" can copy summary and such, but not assignee and approvers

KC Wong_akqwi1

If I create the work item manually, both assignee and approver fields are on the create screen and I can set their values.

My automation rule is triggered on schedule with a JQL. For each matching work item, I create a new work item and copy some fields over.

Screenshot 2026-03-26 102051.png

I tried using the COPY option for Assignee and Approvers at first. Summary and Description are copied, but Assignee and Approvers remain blank.

Then I tried setting a fixed value as above. Still blank.

No error in the audit log, it simply lists the work items created.

Accepted answers

All comments

Trudy P Claspill

Hello @KC Wong

Welcome to the Atlassian community.

Sometimes problems relate to the context of the step within the rule.

Can you please show us the entire rule?

Also show us how you had the fields set when you tried to Copy data into them.

Can you also show us the details in the rule execution log file for the execution of the rule when configured to copy data into those fields?

Are you using the More Options feature of the Create operation with JSON code to set any fields? If so, make sure that none of the fields you selected in the Choose fields to set list are included in the JSON code.

Have you confirmed that the source issue actually has values in the Assignee and Approvers fields? Prior to the Create Item step can you add a Log action to print into the rule execution log the values for the Assignee and Approvers fields to confirm that they have values at the time the Create Item action executes?

KC Wong_akqwi1

The entire rule is:

1. Scheduled to run a JQL "Status = Active", then process each and every one of those issues.

2. A IF block to decide to create new work item or not.

3. The above Create Work Item step. The JSON section is empty.

The audit log just reports success and this:

Screenshot 2026-03-26 111232.png

As said, if I create a work item manually, the Assignee and Approvers fields are seen on screen and I can set the same value as the rule into it.

The rule does copy Summary and Description successfully, while leaving Assignee and Approvers empty.

I tried making the rule actor myself, no difference, so this isn't a permission issue with the automation account.

KC Wong_akqwi1

> Have you confirmed that the source issue actually has values in the Assignee and Approvers fields

The source has values, and that doesn't matter at all when I use a fixed value in the rule and still not work.

Trudy P Claspill

Hello @KC Wong

Thank you for the additional information.

Can you please provide a screen image showing the entire rule. Sometimes there is something visible in the image that is missed when simply describing the rule.

Please also provide a screen image that shows all the details of the Create Item action. If that includes confidential information, blur that portion of the information.

You did not indicate if you are using the More Options area in the Create Item action to set fields with JSON code. Are you?

Please provide the complete details produced in the rule execution audit log, not just the information for the Create Item step.

You said:

when I use a fixed value in the rule and still not work.

You didn't mention that in your original post. Do I understand correctly that when you specify a user explicitly in those fields in the automation rule then the fields are also not getting set in the created items?

Who is specified as the Actor of the Rule? Does that user have the required permissions to set those fields in that project?

I created a simple rule with a Scheduled trigger to run a JQL to get a specific item and Create a new item copying the Summary and Assignee from the item returned by JQL. The Assignee is being set correctly in the newly created item. Automation for Jira is the Actor for my rule.

Screenshot 2026-03-25 at 8.30.45 PM.png

Olga Cheban _TitanApps_

hi @KC Wong !

I can suggest a different approach to this.

Instead of relying on automation rules to copy fields from one work item to another, you could create a reusable template for your work items. In our team, we use our solution Smart Templates for Jira for such cases. The idea is that you save a work item as a template with all the fields pre-filled - summary, description, assignee, approvers, custom fields, and even child work items and checklists (if any).

When you need a new work item, you can create it from the template in one click or set up a schedule to create it automatically. No Jira automation rules needed: this can be handled on Smart Templates' side, although integration with Jira’s native automation is also possible.

Smart Templates - Schedule example - 6 weeks.png

I hope this helps! Let me know if you have any questions.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management