Can't alter time estimate from 0h - "The value could not be saved" error

[Melissa Smith]

Hi all,

Trying to create some tasks ready for the next sprint in Jira but I can't assign a time estimate - it stays at 0h and when I try to enter a time estimate it shows the error message "The value could not be saved". It has been doing this continuously for two sprints now so it is not a temporary issue due to connectivity, However it was working fine in the first sprint we had.

Can anyone advise on how to fix this?

Thanks,

Mel

[Franklin Pang]

Same issue here, the original estimation does not accept any new value.

[Smit Srivastava]

Hi All,

Do we have any resolution for the above-mentioned issue? We started facing the same issue recently. Few people are able to update the 'Original Estimates' and few are not.

[Erin Van Ness]

I'm experiencing this same issue.  I'm an administrator, and this happens when I create a new issue or modify an existing issue.  I've tried updating the estimate from the active sprint and the backlog and it doesn't work in either place.  I am not able to enter any estimates for any issues.  

[Erin Van Ness]

Logging out and logging back in seems to temporarily resolve the issue, but it always comes back.

[Melissa Smith]

Hello,

I am still having this issue six months after my original post (it occasionally intermittently resolves but never for very long), and have taken to just writing the estimated time in the issue name and adding it up myself.

This does mean that I look like I have 0h of responsibilities in my team's charts, though!

Has any work been done to fix this?

[Petter Gonçalves]

Hello Melissa, 

Can you please provide us with a screenshot of the Layout configuration in your next-gen project (Project settings > Issue Types > Select task), as requested before?

I will be checking with our developers internally to confirm if it is related to a bug or something else.

[Brian D. Firfer]

We just had a user also run into the issue of not being able to modify the Original Estimate time value (we are not a next gen project).  Received the message "This value could not be saved." 

After an administrator modified the time for them, they were then able to start modifying the value on their own, and no longer receiving the error.

Has there been any progress on this issue?
Thanks!
Brian

[Petter Gonçalves]

Hello Brian,

Thank you for reaching out.

The problem you referring seems to be different from the one specified in this thread.

As you can see in the bug report, the Time tracking was already implemented for JIRA next-gen and is not causing any issues anymore.

About the problem you are facing, Is it happening for every user in your JIRA site or did it happened just for a specific user?

Since there are no specific permissions that can prevent a user to add the Original Time estimate, I believe the issue was caused by the following bug:

- Time Tracking does not allow to set some number depends on default unit 

Basically, the user could be configured a time format that is not acceptable by the Time tracking field, however, once your site administrator sets the time estimation, he used the same correct format in the field.

Could you please perform a new test with the user and make sure if he is able to set the time tracking using the same format that the Administrator?

[Melissa Smith]

Is there any progress on this issue yet?

I am an administrator on this project yet everyone else in the team does not have this error and can update time estimates fine, it is only my account that is unable to update the time estimates.

Thanks for your time,

Mel

[Petter Gonçalves]

Hello Melissa,

Welcome to Atlassian community.

This is a weird issue. Please, provide us the information below so we can further investigate it:

- Are you using a next-gen project or a classic project?

- If you are in a classic project, can you confirm if the same problem happens in the old issue view?

- If you are in a classic project, navigate to Project settings > Workflows > Click to edit your workflow > Check you have any properties in your workflow status that would be blocking you from edit your issue.

- Have you properly added the time estimate field to your project layout?

Let us know if the steps above help you find the root cause of this issue.

[Melissa Smith]

Hi Petterson,

We are using a next-gen project.

The time estimate field was working fine initially but it no-longer seems to be working.

Please could you advise on how to check whether we have correctly added the time estimate field to the project layout?

Thanks,

Melissa

[Petter Gonçalves]

Hello Melissa,

Thank you for your answer.

Further investigating your issue, I found out that the Time tracking feature is still been implemented on Next-gen project, as it is a beta feature yet.

It is not fully implemented yet and might not be working as expected, as mentioned in the feature request below:

- Time Tracking not available for Next-Gen Software Projects

Our developers are currently making some changes to better implement the feature so I believe that's why you are facing this issue in your JIRA Cloud version.

That been said, I would like to ask you to provide us with a screenshot of the Layout configuration in your next-gen project (Project settings > Issue Types > Select task) and confirm if the problem is happening in other next-gen projects too, just to ensure this is caused by the field background changes and not a different action.

Let us know if you have any other questions.

[Steve Pritchard]

We're seeing this same problem here too - Some users are able to make change to the Original Estimate, while others cannot. They see the same "The value could not be saved" error when they try. 

It is definitely not based on any account settings. We are unable to determine what the difference between user accounts is.

[Melissa Smith]

Ours now works intermittently but not most of the time. I've taken to just writing a time estimate in the task titles and making sure I don't have more than 10 days (the length of one of our sprints) allocated by adding them all up manually.