Jira Cloud Automation: Unable to set “Story point estimate” via JSON although rule runs successfully

[Asaad Askar]

I am trying to automatically set the field "Story point estimate" using Jira Cloud Automation.

Goal:
Calculate and set "Story point estimate" automatically (e.g. based on other numeric fields like A and B).

What I tried:
- Automation trigger: Field value changed
- Action: Edit issue
- Advanced field editing (More options → JSON)

Example JSON used:

{
"fields": {
"Story point estimate": 5
}
}

Result:
- The automation rule executes successfully
- No syntax errors are reported
- No errors appear in the audit log
- HOWEVER, the value of "Story point estimate" is not updated in the issue

Additional observations:
- The field "Story point estimate" appears as a locked/system field
- Reading the field works (Smart Values can access it)
- Writing to regular number custom fields via JSON works
- Writing to "Story point estimate" does not work
- Some community threads show that this JSON workaround works for other users

Questions:
1. Is "Story point estimate" officially writable via Automation JSON?
2. Does Automation follow the same limitations as the Jira REST API for this field?
3. Are there any supported workarounds to set this field automatically?
4. Why does the same JSON approach work in some examples but not in others?

Any clarification or official documentation reference would be appreciated.

[Marc -Devoteam- · Accepted solution]

Hi @Asaad Askar 

Please show your rule and provide details on the actions in the rule.

What type of project are you using team or company managed?

Why is field Story Points not used?

[Asaad Askar]

Hi @Marc -Devoteam- ,

thanks for your reply.

I am using a team-managed project.

My rule is very simple.
The trigger is "Field value changed" for two number fields (A and B).
The action is "Edit issue".

I tried to update the Story point estimate field:
- via normal field selection
- via advanced JSON
- via the custom field ID

The rule runs without any errors, but the value is not updated and remains empty.

Story Points is not used because in team-managed projects the field shown in automation is "Story point estimate" and it is marked as locked.
That is why I tried the JSON workaround.

I can share screenshots of the rule.
The UI language is German, but the rule structure should be clear

[Marc -Devoteam-]

Hi @Asaad Askar 

This json you provided works.

{
"fields": {
"Story point estimate": 5
}
}

In the fields section of the project, is the field mentioned there?

For you calculation you can use:

{{#=}} {{issue.A|0}} + {{issue.B|0}} {{/}}

[Asaad Askar]

Hi @Marc -Devoteam- 

I’m already using the same math expression approach you suggested, with {{#=}} and |0 as fallback values.
I’ve tested the following cases:

A and B both empty

One field empty, the other set

Both fields set

All cases work as expected now.
Thanks also for the tip about the log action – that helped during debugging.

[Marc -Devoteam-]

Hi @Asaad Askar 

If my answer helped solving your question, please accept it as it can help others with the same problem

[Duc Thang TRAN · Accepted solution]

Hello @Asaad Askar 

Can you try with the custom field ID of this field?

Ex : where id of Story point estimate is customfield_10344

{
"fields": {
"customfield_10344": 5
}
}

There are a few ways to find a field ID https://confluence.atlassian.com/jirakb/how-to-find-any-custom-field-s-ids-744522503.html -> I prefer using the REST API. 

rest/api/3/field/search?query=Story point estimate

Hope this can help 

[Asaad Askar]

Hi @Duc Thang TRAN, thanks for the suggestion,

I tried the same approach using the custom field ID to set the Story point estimate value, but in my case the value is not updated, even though the rule runs without errors.

My project is a team-managed project.

Could it be that this workaround only works for company-managed projects, and that in team-managed projects the Story point estimate field cannot be updated via Automation or JSON??

I Just want to confirm whether this behavior depends on the project type.

[Duc Thang TRAN]

Hello @Asaad Askar 

I had just forgotten that Story Point Estimate is a  field for Scrum team-managed projects , but I didn’t have any issues updating it through automation in a team-managed project.

Do you see in the ticket history any automation that made an action on this field?

[Asaad Askar]

It seems that the update works in team-managed Scrum projects when the field is set correctly.

Could you tell me how it worked out?

I tried to calculate it automatically as follows:
{
"fields": {
"customfield_10016": {{issue.A|0.plus(issue.B|0)}}
}
}

[Duc Thang TRAN]

@Asaad Askar 

What are the data types of fields A and B? Also, you have a field named A & B. Doesn’t that create confusion?

Here is an example of a math expression I’m using. You can use it as inspiration.

{{#=}} {{issue.Account Name|0}} + {{issue.Effort|0}} + {{issue.Story Points|0}} {{/}}

Tip: Add a log action to check and to verify that the syntax is correct

Hope this can help

[Asaad Askar]

Hi @Duc Thang TRAN ,

thanks for your reply.

Fields A and B are both number fields.
I agree that the naming could be confusing – I’ll consider renaming them to something clearer.

I’m already using the same math expression approach you suggested, with {{#=}} and |0 as fallback values.
I’ve tested the following cases:

• A and B both empty

• One field empty, the other set

• Both fields set

All cases work as expected now.
Thanks also for the tip about the log action – that helped during debugging.