I can't edit my issues story point estimates
Asked by Fernanda Donnini:

When I try, it gives me an error message saying the item might not be editable and that I might not have permission (weird since I created the account and project myself).

I'm on a team-managed software project type (Software Project) and a Free plan.

![Screenshot 2024-07-22 at 19.19.50.png](/t5/image/serverpage/image-id/337098iE30C3193F6692577/image-size/large?v=v2&px=999 "Screenshot 2024-07-22 at 19.19.50.png")


Answers:
author: Trudy Claspill
body: Hello [@Fernanda Donnini](/t5/user/viewprofilepage/user-id/5549513)

Welcome to the Atlassian community.

Your post tags indicate you are using the Free product plan. Is that correct?

Are you able to edit other fields displayed in the same issue's details?

Are you able to edit the field in any other issue?

What type of issue is it? What is the status of the issue?

comments: author: Fernanda Donnini
body: Thank you for replying.

Yes, I'm using the Free plan.

Yes, I'm able to edit all other fields except this one.

I've tried editing the story points estimates on other issues, and it's the same behavior (blocked).

The issue type is Story. I've tried on different issues with different statuses, from wishlist/todo to done and everything in between. Nothing works.


author: Trudy Claspill
body: Thank you for the additional information, Fernanda.

Are you able to edit Story points estimate field in other Team Managed Software projects?

What steps were you taking when you got the error message? Were you viewing a single issue details screen and trying to edit the field? Were you using a Bulk Change operation? Were you in the List view trying to edit fields?

The original Story points estimate field should be editable. If it is not, the root cause for the problem needs to be found and addressed.

I would not recommend following [@Valerie Knapp](/t5/user/viewprofilepage/user-id/4929946) 's workaround suggestion (sorry, Valerie). You would not be able to use another custom field as your Estimation option for the board, and you would not be able to base board burndown charts on the custom field.


author: Valerie Knapp
body: Lol, no problem [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) , we're all on the same team here, just trying to get something that works. Good luck [@Fernanda Donnini](/t5/user/viewprofilepage/user-id/5549513) !


author: Valerie Knapp
body: Hi [@Fernanda Donnini](/t5/user/viewprofilepage/user-id/5549513) , welcome to the Atlassian Community and thanks for your question!

Even though it is a team-managed project, the field 'Story Point Estimate' is a standard, system field.

![Screenshot 2024-07-22 20.11.47.png](https://community.atlassian.com/t5/image/serverpage/image-id/337119i1D9E0EACF809E7AF/image-size/large?v=v2&px=999 "Screenshot 2024-07-22 20.11.47.png")

You could create your own, as I am showing below, but this probably explains why you can't modify it

![Screenshot 2024-07-22 20.14.30.png](https://community.atlassian.com/t5/image/serverpage/image-id/337121i517D24D3BAB08C14/image-size/large?v=v2&px=999 "Screenshot 2024-07-22 20.14.30.png")

Please share your feedback if my suggestion is helpful.

Cheers

comments: author: Fernanda Donnini
body: Thank you, Valerie. The solution you propose would be to create a new custom field and add it to my issues, correct?


author: Valerie Knapp
body: Hi [@Fernanda Donnini](/t5/user/viewprofilepage/user-id/5549513) , thanks for your reply. Yes, basically the solution I am suggesting is a workaround to allow for you to have the Story Points Estimate field configured how you would like to use it, as I fear that the original field, even in the team-managed project, will not be editable / customizable.

Cheers


author: Fernanda Donnini
body: I see - I will try this then thanks. Do you happen to know what's the point of having the original Story Points Estimate field if it's not editable? Or is this just restricted in the free plan?


author: Valerie Knapp
body: Hi [@Fernanda Donnini](/t5/user/viewprofilepage/user-id/5549513) , thanks for your reply. I had understood this is just a behaviour of a standard system field used in a team-managed context. I think if you wanted to change the Summary or Description fields, you would find the same limitation.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/337293i13BF5E4D7182425B/image-size/large?v=v2&px=999 "image.png")

For example, I see this message in one of my team-managed projects \^. I agree it could be clearer if this is the same case for the Story points.

Cheers


Tags: cloud

jira-cloud