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 Not Carrying Over Field Values to Issue Created in Another Project

joanna.natial

Hi Community,

I'm having an issue with a Jira Automation rule and would appreciate any guidance.

I've created an automation rule that checks whether certain fields are not empty. When the conditions are met, the rule creates a new request in a different Jira project and is intended to copy all populated field values from the original issue to the newly created issue.

The issue is that the new ticket is being created successfully, but the field values are not being carried over. The corresponding fields in the new issue remain empty.

Please see below screenshots of my autimation build.

Screenshot_12-10-2026_101437_centuriacapital.atlassian.net.jpeg

Accepted answers

All comments

Matthew Sinclair

2 things to try/check:

1: Insert a "re-fetch" command after you create the work item.

In automation - during the flow's "Execution" - its a snapshot in time - if you change the system up with say a "New Ticket" - it won't see it until you "Refresh" the browser so to speak - "Refetch" does this.

You don't always have to do that but sometimes it solves these weird situations. If it doesn't - keep going.

2: Make sure the fields you are writing are on the "Edit Screen" of the target space. That and your actor has "browse issue/edit issue" permissions (if your not using the usual Jira Automation Actor)

I'm assuming scope is good because you said it created the ticket successfully - but make sure the scope is just those 2 spaces (main/target) - don't need it to be global.

Post Thought: The only other thing I'm thinking may be causing problems is your Branch - I would think you want it to say "most recently created item" as opposed to related - it should qualify in this context.

Something to consider as a 3rd thing I guess?

Hope this helps.

Trudy P Claspill

Hello @joanna.natial

When a rule is not producing the results you expect it is helpful to us if you provide the details of the rule execution log.

Can you share the details of the Create Work Item action? That is where you should be setting the created work item's values to values from the trigger issue.

What is the purpose of the branch for Linked Work Items? Which work items are you trying to affect

Shaik Riyaz

Hi @joanna.natial ,

The fields are not being copied because of the current execution order in your Jira Automation rule.

Root Cause

Your rule is currently structured as follows:

A new work item is created in the destination project.
The rule enters the branch For: Linked work items (Type: Relates to) and attempts to run the Edit work item fields action.
The Link work item to: Most recently created work item action is executed at the end of the rule.

Since Jira Automation processes actions sequentially from top to bottom, the newly created work item has not yet been linked when the branch executes. As a result, the branch does not find any linked work items and the Edit work item fields action is skipped.

Solution:

Rather than relying on an issue link to identify the newly created work item, use a branch that directly targets the work item created earlier in the rule.

Steps

Remove or replace the current For: Linked work items branch.
Add a Branch rule / Related work items component.
Configure the branch as:
- Type of related work items: Most recently created work item
Within this branch, add the Edit work item fields action.
For each field that needs to be populated (for example, Operating Bank Account Details, Operating Bank Account Name, Allocated BSB, etc.):
- Select Copy from → Trigger work item, or
- Use smart values such as: Plain Text{{triggerIssue.FieldName}}
If you still require a relationship between the two work items, retain the Link work item to action and place it either before or after the branch, depending on your process requirements.

Thanks!!

joanna.natial

This is my automation buikd and still not working.

Screenshot 2026-10-12 144902.png

Shaik Riyaz

Hello

By default, many automation rules run under Automation for Jira. If the fields being updated have project-level, issue-level, or field-level permission restrictions, the default automation actor may not have sufficient access to read or update those fields.

Please try the following:

Open the automation rule.
Select Rule details.
Check the Actor field.
Change the actor from Automation for Jira to your user account.
Save and publish the rule.
Run the test again and review the audit log for any differences.

If the rule works when executed under your account, this will indicate a permissions-related issue with the current rule actor rather than a problem with the automation logic itself.

Thanks!!

Matthew Sinclair

Please check my suggestions and get back to me/us on how it did.

Trudy P Claspill

Hello Joanna,

Please provide a screen image showing the details of the rule execution Audit Log for when the rule ran. This provides vital information to debugging why you are not getting the expected results.

Make sure to click all the ">" characters next to lines in the log to expand each one to show its details.

joanna.natial

Here is the Audit log

Screenshot_13-10-2026_82239_centuriacapital.atlassian.net.jpeg

Trudy P Claspill

Hello @joanna.natial

Thank you for sharing the rule log file details.

Please check the Space Scope for the rule by clicking the … button above the rule and selecting Settings.

That should give you something like this:

Does your rule show that you have Singe Space for the Scope and the BA space in Spaces?

I think the problem you might be encountering is that the Space Scope for the rule probably doesn't include the CSS space where your rule is creating the new issue. Rules can access only the issues within the space(s) listed in the Space Scope for the rule. You would need a Global or Multiple Space scoped rule that includes both the BA and CSS spaces in order for the Branch action to be able to find the CSS issue created by the rule.

The Create Work Item and Clone Work Item actions are exceptions to the Space Scope limitation. It is allowed to use those actions to create a work item in a space that is not within the rule's scope.

Global and Multiple-Spaces scoped rules can be created and managed only by Jira App Admins through Settings (the cog icon next to your avatar) > System > Global Automations. If you don't have that level of access you will need to work with your Jira App Admins to get the rule modified.

Matthew Sinclair

You still have not finished checking my suggestions or others - need to do the things before we can "sus" out what's causing your headaches.

joanna.natial

it's still not copying the values of field to the created link tikcet

Screenshot_13-10-2026_125137_centuriacapital.atlassian.net.jpeg

Shaik Riyaz

Hi joanna,

Could you please change the automation rule actor from Automation for Jira to your user account and test it again once?

Thanks!!

Markus

Hi @joanna.natial,

To troubleshoot why your Fields are not getting copied, I would try to log if you are actually getting the right Data from the trigger Work Item. Create a new action at the end of the Automation with 'Log action' then input:
Bank Acc Details: {{triggerIssue.Operating Bank Account Details}}, BSB: {{triggerIssue.Allocated BSB}}
With this you analyze the Data you are writing to the new Work Item. If these are Empty then your Issue mostly likely revolves around not reading the Fields correctly, hence the Fields stay Empty.
If the Log is displaying the right Data, then Issue is that you are not writing. As the others pointed out this may have to do with permissions, automation scopes, screen schemes or other config problems outside of the automation.
Putting the afflicted Fields into a variable and/or logging what you trying to write can help you narrow down the problem you are facing. Not reading the Fields requires a different solution than not writing. Identifying the Issue will point you in the right direction.

Best Regards,
Markus

Gabriela - LeanZero

Hi Joanna, I rebuilt your rule on a test site and got your audit log line, "No related issues could be found", from a single-space rule, whichever branch I used: linked work items, most recently created or JQL. Swapping the branch type can't fix it. With the second space in scope, as Trudy described, the same branch worked unchanged.

You can drop the branch and do what Trudy suggested in her first reply: set your five fields inside "Create work item with a request type", copied from the trigger work item. That worked for me with the rule's scope left alone.

That action only filled fields that are on the request type's request form. A field that was on the work item's screens but not on that form got skipped, with "Some errors" logged and the field listed as ignored, until I added it to the form. Atlassian's doc: "Available fields include all fields that are not hidden and added to the request type." https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/

Are your Allocated BSB, Settlement/Member ID and the rest on the CSS request type's form?

Evelin Bayer - codefortynine

Hi @joanna.natial ,

It might be worth looking at this from a different angle. As you've noticed, copying field values with native Jira automation can get tricky, as every field you want to copy has to be mapped and maintained individually.

If you're open to using a Marketplace app, you could give Deep Clone for Jira a try.

There's one basic difference between your current setup and Deep Clone:

With "Create work item", nothing is copied unless you set it.
Deep Clone works the other way around: it copies the work item including including fields and content, and you exclude what you don't need.

Instead of creating a new work item and setting each field, Deep Clone clones the trigger work item into CSS, and you decide which fields to clone. That way, you don't need a branch to edit the new work item afterwards.

Create a Deep Clone preset with CSS as the target space and your configuration, including any field edits.
Replace "Create work item with a request type" and the branch with the Deep Clone – Single Clone action.
Enter {{issue.key}} as the Source Work Item Key and select your preset.

See our documentation for more details.

Full disclosure: I work for codefortynine, the vendor of Deep Clone for Jira.

Welcome!

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

Quick Links

Find more posts tagged with

field

automation

jira-service-management