"Story Points" Not Appearing

[Augusto Romaniuk]

I changed the estimate to "Story Points" but the field still asking for TIME (Weeks, Days and Hours) 

[Walter Buggenhout]

Hi @Augusto Romaniuk and welcome to the Community!

Yes. You have updated the estimation statistic of your board, but that does not do anything about the fields on your screens. Estimativa original (or Original estimate) is a distinct field that will always ask for a time value. If you want story points, you'll need to add the story points field to your issue screens.

See this support article on screen configuration and also This support article on configuring issue layout as you might have to look at both.

Hope this helps!

[Augusto Romaniuk]

Yeah, i added the story points field to my screen, but stills not appearing in the issue.

Here is a printscreen that shows the story points field active in my default screen. But, in the issue, this field doesnt exist.

[Trudy Claspill]

Hello @Augusto Romaniuk 

Welcome to the Atlassian community.

Check the Issue Layout for that issue type in that project.

It is possible to place fields in an "Hide when empty" section in the Layout, in which case if the field has no value it would not immediately display on the issue.

And the empty fields will show up in the More Fields section when viewing the issue.

If you want it to always display in the issue view even when empty, in the Layout drag the field above the "Hide when empty" line.

[Augusto Romaniuk]

Thank you! Now I can set the story points. But where is located the story points estimate? For me just shows the "Original Estimate". 

[Trudy Claspill]

There are two customization structures for Jira Cloud. One is for Company Managed projects, where must of the customization have to be managed by a Jira Administrator. The other is for Team Managed projects, where the customizations can be managed by the Project Administrator.

Only one system-provided Story points field is used in each of those.

Company Managed projects use the supplied "Story Points" field.

Team Managed projects use the supplied "Story points estimate" field.

You use one or the other, based on your project type. You don't use both in one project.

It is unknown why Atlassian choose to use two different names for the field.

Typically the story points value is always considered an "estimate" in the agile methodology. It would be atypical to have an estimate for story points and then a "final" adjusted value for story points. Is there a reason you feel you need both an estimate and a final adjusted value for story points?