Help with automation in JIRA Cloud

[Erika Reategui]

Hello everyone,

I hope someone can help me with this issue. I’ve spent a lot of time trying to figure it out, so I decided to reach out to the Atlassian Community.

I built an automation to update a custom field on a linked issue in a Discovery Project whenever a custom field on the Discovery Project is updated or edited. My goal is for the same value added to the custom field on the Discovery Project to also be added to the custom field on the linked issue.

I should mention that both custom fields has the same name.

Discovery Product Project

"Quarterly Rank"customfield_11283

Linked Item

"Quartely Rank" customfield_11976

This is how I built the rule

==========================

I am getting the following error on the rule

Field value changed10/22/2025, 13:18:33

BRANCH

Branch rule / related work items10/22/2025, 13:18:33

Edit work item10/22/2025, 13:18:33

We encountered multiple fields with the same name and type:

Quarterly Rank (com.atlassian.jira.plugin.system.customfieldtypes:float)

Issues edited successfully

VIF-7709

Spaces:

DPP. SPP

The error message says that there are multiple fields with the same name, but there aren’t. Even though the automation shows that the issue was edited, the value is not being added to the custom field on the linked item.

Can someone help me figure out how to make this work?

Thank you!

[Bill Sheboy · Accepted solution]

Hi @Erika Reategui 

Are your work items in different projects: the JPD project and another one for the linked item?

If so, please note even though the fields have the same name, they are different in the configurations for those projects.  The rule will need to use a JSON expression to copy the value rather than use the field dropdown list in the Edit Work Item action.

What are the types for your fields?  Knowing that will help the community offer specific suggestions on making the edit.

Kind regards,
Bill

[Erika Reategui]

I am trying to responde but I keep getting the error below

There was invalid HTML in the message body that has been removed. If you're posting a link, add the hyperlink using the editor.

[Erika Reategui]

Hello Bill Sheboy

Thank you for your response.

Yes, they are in different projects, and I understand that the fields are not the same each one has a different ID. I also used a JSON expression provided by Rovo. I included the JSON code in my original report.

Unfortunately, I’m not able to include any visuals or screenshots to show the code I used, as I keep getting the error mentioned in my previous message. It’s quite frustrating not to be able to share that information directly.

[Erika Reategui]

[Erika Reategui]

I was finally able to upload an image showing the code I used to create the rule. Could you please review it and let me know what I might be doing wrong? We really need to have this rule working as soon as possible. Thank you.

[Bill Sheboy]

Hi @Erika Reategui 

From what you show, there is definitely something incorrect in either the rule export or the JSON expression you used.  Let's try this:

• What are the types of these fields: text, number, select-option, etc.?
• Please post the JSON expression you are using as plain text

[Erika Reategui]

Hi @Bill Sheboy 

They are numeric numbers, here is the JSON expression.

=================

{

  "name": "Copy Quarterly Rank from Roadmap to VIF Linked Issues",

  "projects": ["ROAD"],

  "trigger": {

    "type": "FieldValueChanged",

    "fieldIds": ["customfield_11283"]

  },

  "actions": [

    {

      "type": "Branch",

      "branchType": "relatedIssues",

      "relation": "linkedIssues",

      "conditions": [

        {

          "type": "project",

          "projectKey": "VIF"

        }

      ],

      "actions": [

        {

          "type": "EditIssue",

          "fields": {

            "customfield_11976": "{{#=}}{{triggerIssue.customfield_11283}}{{/}}"

          }

        }

      ]

    }

  ]

}

[Erika Reategui]

Thank you for your help 

[Bill Sheboy]

Thanks, @Erika Reategui 

In the Edit Work Item action, you would only need this to set the value:

{
  "fields": {
    "customfield_11976": {{triggerIssue.customfield_11283}}
  }
}

[Erika Reategui]

it worked!!!!! thank you soooo much Bill. :). Have a great day!!