Estimation feature is disabled but Story Points Estimate still available for the issue.

[011_avinash]

Hi

I have disabled the Estimation feature in the Project Setting page in the Team Managed project. But, I am still able to see and enter the details in Story Points Estimate and Original Estimate fields in the issue. Can someone please help with their input? My understanding is that, user should not be able to see tory Points Estimate and Original Estimate fields if the Estimation feature is disabled in the Project Settings -> Feature.

[Bill Sheboy · Accepted solution]

Hi @011_avinash 

Please ask the project admin to remove the fields from the view configuration if the team does not want to see them.  They can be dragged off of the view, over to the right-side of the configuration view.

https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/

Kind regards,
Bill

[011_avinash]

Thanks @Bill Sheboy for responding. Actually I was thinking that if Estimation features itself is disabled (in Project settings -> Features) then, user should not be able to see the Story Point field and Original Estimate field at all.

@Walter Buggenhout sorry to pull you here out of no where. But can you please help ? :)

[Walter Buggenhout]

Hi @011_avinash,

Toggling the estimation feature on/off does normally indeed add/remove the story points or original estimate field.

However, nothing prevents you or another project admin to manually add the same fields to your issue type screens. I have been able to reproduce that scenario myself by disabling the estimation feature, but then manually adding the fields to the screen associated with an issue type.

That is most likely what happened in your case as well. Enabling the estimation feature would normally enable the story point estimate OR original estimate field, not both.

So, as @Bill Sheboy mentioned, just navigate to project settings / issue types and remove the fields from the screen. That should make them disappear. 

[011_avinash]

Thanks @Bill Sheboy and @Walter Buggenhout  for helping with you input :)