What is the deal with Story Points ???

[Dinu Radian]

I am a bit of an old-timer with JIRA using the Classical project model (10+ years)

It was a time when effort estimates expressed in Story Points or Time could be made only while issue was in the backlog. Has that changed? I see for the Cloud version the Story Point field can be edited even after the issue reaches Done status (?!). What is the point of having an estimate for velocity reference if one can modify that estimate at any time after the sprint started???

Can I trust the Version Chart forecast, if Story Point estimates can be modified willy-nilly at any point in time?

[Petter Gonçalves]

Hello @Dinu Radian

Thank you for reaching out.

Indeed, Jira has been modified to fit for all the several use-cases of our customers. Talking about the ability to edit Story points after an issue is closed, it allows the project manager to correct any wrong estimation for the current board.

Anyway, if your scenario needs the Story point field to be uneditable once the issue is closed, you can use workflow properties to restrict it. These would be the steps:

1. Navigate to your project > Project settings > Workflows > Edit
2. In diagram mode, Click in the status/transitions where the Story points should not be editable > Properties:
   
3. Add the property jira.issue.editable with the value false:
4. 

The steps above will block any issue that uses that workflow from being edited in the statuses with that property.

Let us know if you have any questions.