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

[Dan McLean]

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. 

[Aaron Geister · Accepted solution]

@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

[Dan McLean]

I'm not quite sure what my next steps are/the query to revert the number back to the original estimate. I have:

When: The value changes for story points

If: status matches (everything but "todo")

Then: Edit issue fields story points  {{issue.Story Points}}{{fromString}}

It runs, but doesn't revert the points back to the previous total

[Dan McLean]

I also tried it using copy story points from trigger issue and that seemed to work a little, although it seemed somewhat spotty and didn't always kick off the automation

[Dan McLean]

nvm figured out the query {{fieldChange.fromString}}

[Aaron Geister]

I was going to say you would need to use {{fieldChange.fromString}} you might want to also have another condition that is a advance compare condition. But not sure that would work from the same issue that is usually compare two different issues or fields.

[Aaron Geister]

I forgot to mention in the edit field Story Points you can put the smartValue {{fieldChange.fromString}} and that should pull the change data back to what it was in the edit of the field story points>

I would try that to see if it makes the change for you.

[Mikael Sandberg]

Hi @Dan McLean,

Welcome to Atlassian Community!

You would need an app in order to do that, out-of-the-box Jira do not have field level permissions. The Marketplace have a handful of apps that can do this. 

[Marc - Devoteam]

Hi @Dan McLean 

You can only prevent this by removing the Story Point field from the edit screen. This will mean you can't edit the field in any status.

A work around can be to add transition on status backlog. this transition will go from status backlog to status backlog, put a screen on the transition with the Story Point field on it.

Do this for every status where you will grant the option to change the Story Points and not on statuses where the points should not change anymore.