Is there a way to restrict editing of just the story points field after an issue moves to in progres

Dan McLean_1z1xng

So for context I am attempting to prevent users from editing just the Story Point field of an issue, once that issue moves from "backlog" "to do" and into a form of "in progress". 

 

I followed the directions in a similar community post (1867467) But it does not seem to have any effect on the story point field in Jira, does this solution only work for custom fields and not for native fields? 

 

Wondering if anyone has found a solution to just locking this one field. 

A A Ron Geister _Trundl_

@Dan McLean 

Welcome to the community and hope this finds you well. We are happy to have you here with us.

So as stated there is app add-ons that can help with this and you could use. I am also thinking that you can make an automation that would help to monitor this issue and replace the value back to what it was after its been moved to a new status.

Automation idea:
Trigger: You can monitor for change to the field sprint

Condition: If specific status

Then you can use compare field condition

Then use the action to edit the trigger issue


Here is another community post that references this same idea but with an email send.
https://community.atlassian.com/t5/Jira-questions/Automation-Email-using-Old-Value-and-New-Value-of-a-field/qaq-p/1844957

I hope this helps and if it does please mark as answered and if it doesn't lets talk in more depth and what I can assist with.

Respectfully,

Aaron