nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I can't edit my issues story point estimates

Fernanda Donnini_m52aeb

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

Accepted answers

All comments

Valerie Knapp_dpp5c6

Hi @Fernanda Donnini , 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

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

Please share your feedback if my suggestion is helpful.

Cheers

Trudy P Claspill

Hello @Fernanda Donnini

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?

Fernanda Donnini_m52aeb

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.

Fernanda Donnini_m52aeb

Thank you, Valerie. The solution you propose would be to create a new custom field and add it to my issues, correct?

Valerie Knapp_dpp5c6

Hi @Fernanda Donnini , 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

Fernanda Donnini_m52aeb

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?

Trudy P Claspill

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 '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.

Valerie Knapp_dpp5c6

Lol, no problem @Trudy P Claspill , we're all on the same team here, just trying to get something that works. Good luck @Fernanda Donnini !

Zlatan Sarkotic

I have used a couple of hours on researching different solutions. Basically I think that there is a bug when you import something with external file. So the only solution that worked 100% for me was to create a new space/project and transfer all of the items from backlog to the new project. Now everything works. Hope it helps and have a good day .

kh_jbau

Hi Zlatan, this topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have additional questions, we encourage you to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our Community Guidelines.

Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud