New generation - estimation feature

[Zofia Safteruk-Przybysz]

Hi,

I'd like to ask for help with some clarifications for New Gen Jira. 

1. I would like to understand if the estimation feature only supports story point estimation? If we put days/hours instead would that still work or we may experience some issues down the line? 

2. If I replace default field "story point estimation" with a numerical custom field "task estimation" would it work in the same way? 

3. Also I don't understand from the documentation how the estimation feature impacts the reports. Could you please help with some example/detail? 

Thanks,

Zofia

[Petter Gonçalves · Accepted solution]

Hello @Zofia Safteruk-Przybysz

Welcome to the Atlassian Community!

I will try to bring you some concepts so I can try to clarify your questions and confirm we are on the same page:

1. I would like to understand if the estimation feature only supports story point estimation? If we put days/hours instead would that still work or we may experience some issues down the line? 

Indeed, the estimation feature of Next-gen boards only considers Story points for now, as mentioned in the documentation below:

- Estimation in Next-gen Boards

We have the following feature request opened to also consider time estimate on the board and reports:

Provide time estimation for Next-gen Projects 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

2. If I replace default field "story point estimation" with a numerical custom field "task estimation" would it work in the same way? 

The Story Point Estimation is the only field that is considered as the estimation metric in Jira next-gen boards and Reports, so it does not allow other fields to be used as estimation metrics. Basically:

- Use the Story Point Estimation for Next-gen issues.

- Use the Story Points fields for classic issues.

3. Also I don't understand from the documentation how the estimation feature impacts the reports. Could you please help with some example/detail? 

Basically, each report of Next-gen displays a customized graphic and amount of data to help you see the results you had in your last Sprint or current release. Giving you a practical example:

Let's suppose you have configured a Next-gen Burnup report based on your Story points. This report shows the amount of work that has been completed (Story points of done issues) and compares it with the work that was planned (The Story points of ALL issues in the Sprint).

For more details on how each Next-gen reports work with Story points, you can check the documentation below:

Enable Reports in Next-gen 

Additionally, I would like to let you know that Next-gen projects provide a streamlined experience, are easier to use, and quicker to set up than classic projects, however, it have fewer customization options to keep it simple to all the teams. 

Let us know if you have any questions.

[Zofia Safteruk-Przybysz]

Thank you, Petter, for the answers. Very helpful. 

Story Point Estimate seems to work simply as a number. So if I put days there it should still work for me. 

I am looking forward to how you will expand next-gen jira so it stays simple but provides enough flexibility. I find portfolio view very important. I tried to use Dashboard widgets as a workaround and filter by multiple projects but it does not work well and each project's issuetype is treated as a unique issuetype.... I'll check if there is another thread in the community on this. 

[Petter Gonçalves]

Hello @Zofia Safteruk-Przybysz

You are welcome!

In fact, we are working to improve Next-gen template and get it with similar features that Jira Classic does, however, giving the option to turn these features off and on in Next-gen.

In Jira Next-gen, you are correct to say that all the issue-types are referenced as unique since each next-gen project uses dedicated entities.

Please, feel free to open a new question about this subject if you need any specific help.