Copy Custom Field (Numeric) from Jira Product Discovery into Jira Software, same custom field

[Sandy Tang]

Hi all 

I'm trying to copy a custom field from Jira Product Discovery, to Jira Software, using the same Global Field, but my jira automation isn't working - it says it's successful, but doesn't actually update the ticket;

Trigger: When value changes for custom field (number)

If work item matches a specific type of ticket in JPD

Branch: For linked work items, type is 'implemented by' 

If work item matches a specific type of ticket in JSM

Then Edit work item - copy custom field 

I get a Success, but not the actual action. 

Any ideas?

Thanks

[Walter Buggenhout · Accepted solution]

Hi @Sandy Tang,

It's already quite good that you're describing the steps included in your automation rule. But do share screenshots of your entire configuration.

Issues that may be occurring are:

• what exactly you are copying from / to in the edit work item step. You should be copying the field from the trigger work item there;
• the scope of your rule as you are working across multiple projects (unlikely, since you say there's no error in the log. 

[Sandy Tang · Accepted solution]

Hi 

thanks for the information, here's the rule, and here's the audit log;

I have a feeling it has something to do with the fact that when you type in the numeric number, Jira automatically changes it from e.g. '14000' to '14,000' with a comma, so I'm wondering whether it's because of that it's not copying across properly, even though it's using the same global field. 

any more thoughts?

[Hari Krishna]

Thanks for sharing the screenshots, @Sandy Tang  — that really helps.

The comma formatting (14,000) isn’t actually the issue here. Jira automatically adds commas in the UI for readability, but internally the numeric field value is stored as a plain number (14000.0). Automation reads and writes this raw value, so formatting shouldn’t block it from updating.

Here are a few more points to check based on your audit log:

Audit log shows “Issues edited successfully” — this means Jira Automation did find and attempt to update the linked issue.

If the value still doesn’t appear in the Jira Software issue, it almost certainly means the field isn’t displayed on the Edit or View screen of that issue type, or the context doesn’t include that project.

Try logging the field value explicitly before edit

Add a “Log action” right before the “Edit issue” step with:

{{triggerIssue.customfield_XXXXX}}

This confirms the value being passed.

Force-update using a smart value

In the “Edit issue” action, instead of “Copy from trigger issue,” use “Set value” → {{triggerIssue.customfield_XXXXX}}.

Sometimes Product Discovery fields behave slightly differently in copy mode, so setting via smart value bypasses that.

Field type compatibility

Double-check the custom field type is exactly Number Field in both projects. Some JPD numeric fields use an “idea property” format that doesn’t fully sync across other project types.

If that’s the case, try creating a new shared “Number Field” in Jira (non-JPD type) and use that one instead.

[Hari Krishna · Accepted solution]

Hi @Sandy Tang ,

It sounds like your rule is running successfully but not actually updating the linked Jira Software issue. This usually happens when the target field isn’t properly configured or accessible in the project where you’re trying to update it. Here are a few things to check:

1. Field context
Even if the field is global, confirm that its context includes both the Jira Product Discovery (JPD) and Jira Software (JSW) projects.
Check under:
Jira Settings → Issues → Custom Fields → [Your Field] → Contexts and default value
If the field is restricted to one project, Jira Automation will not update the other issue even though the rule shows as successful.

2. Field on the screen
Make sure the custom field is present on the edit/view screen of the target Jira Software issue. Jira cannot update fields that aren’t on the screen.

3. Linked issue direction
Confirm the link direction in your branch. For example, if you used “For linked issues → implemented by,” ensure that the JPD issue truly has that link type in that direction. Try adding a “Log action” inside the branch to confirm that a linked issue is being found.

4. Copy method
When editing the linked issue, use “Copy from → Trigger issue → [Field name]” instead of manually entering a smart value like {{triggerIssue.fieldName}}. Some JPD fields have internal references that don’t map cleanly to JSW.

5. Field type differences
Certain JPD fields (especially number or idea-based fields) are specific to JPD and don’t behave exactly like standard Jira fields. If that’s the case, create a new number field in Jira (non-JPD) and use that across both projects, or manually copy the value using a smart value expression in the “Edit issue” action.

6. Audit log
Check the detailed audit log in your rule. If it says “No issues matched the condition in branch,” your linked issue isn’t being found. If it says “Edit issue successful” but no change is visible, it’s most likely a field context or screen configuration issue.

[Sandy Tang]

I'm pleased to say, I managed to get this working 😁

Not much different other than I used Advanced fields in JSON and it just worked (I swear I had tried this and it didn't work...).  Also I'm re-reading my log action and pretty sure it's referencing the same field 😅 but it worked, so I'm happy 🤣