Converting story point estimates to story points

[niks.berzins]

Hi there,  I'm somewhat new to Jira, so some of the terminology might be a bit off.

We're managing several projects in a single sprint. Some of the projects are classical and others are next-gen.

The classical projects have a field "story points", and the next-gen ones have a field called "story point estimates". Currently on the sprint board we can see tasks from both, but the story points only show up for classical projects (where the field is story points).

For next gen projects, the "story points estimate field" appears empty when looking at the board. When opening a task I can see that the field has a value saved in it.

Is there a way to equalize this across old and new projects? Couldn't find a way to add the "story points" field to next gen, but also couldn't find a way to add the "story points estimate" field in classical projects. I'd just like to have the same field across projects, and I am fine with manually doing that for tasks, is there a way to do it?

[Pramodh M]

Hi @niks.berzins 

As I have already referenced. 

Please track the Issue here

https://jira.atlassian.com/browse/JSWCLOUD-17173

Till then it's better if you manage Story Points for the projects at the individual level. Don't burden yourself by manually doing the things

Thanks,
Pramodh

[Bill Sheboy]

Hi @niks.berzins -- Welcome to the Atlassian Community!

Trying to centralize the story point values between the different project types, Company-Managed and Team-Managed, may lead to some unintended consequences and Jira reporting problems.

You noted this: "We're managing several projects in a single sprint."

What do you mean by that?  For example:

1. Each team's project has a Scrum board they manage for their sprint, and we are viewing those on a combined board just for visibility across teams.
2. Each team's project ignores any boards in their project, and we use a combined board with a sprint to manage the work in one place...and so the teams are essentially on one large Scrum team.

If it is #1, why would you show story points from different teams on one board?  That would not seem helpful to me.  However just seeing the work progress (perhaps as a Kanban view) may be helpful.

If it is #2, why not just use one project and avoid this problem of incompatible fields...and potentially incompatible workflow between projects?

Thanks, and kind regards,
Bill

[niks.berzins]

Hey Bill,

I think it's scenario 2. We have several ongoing projects that need some attention every month and the same team working on them. It's one software solution, that is being adjusted for different clients. The endusers have JIRA access for their project, thus different projects for the same deveoper team.

I've attached a picture of what we got, so it's clear. 

In this view the task at the bottom right has "story points" field and the number is visible in this view. The tasks above have "story points estimate", and show the grey box as "-" because it's a different field. If I open the task the "story points estimate" field does have a value saved there.

I assume it's because the board settings offer you to choose time estimation, and shows only that field. So what I want is to use the same field across old and next-gen projects. Regardless of weather it's the "story points" or "story points estimate". Is there a way to use the same field for both new and old projects so I can view them like show in the picture? Because I couldn't find a way to add "story points estimate" field to the old projects, or the "story points" field to the next-gen ones.

[Bill Sheboy]

Working as you note, this may be challenging. 

I have seen posts of people trying to work-around this with automation rules, etc.  Yet you are trying to get Jira to have consistent behavior/reporting for different fields in different project types...and that may not work.  As others have noted, there is a suggestion under consideration to "fix" this design choice.

A better work-around for now would be to only use company-managed projects, and then merge for one sprint in a company-managed project board.

[Pramodh M]

@niks.berzins 

Please find the details on what Story Points Estimate and Story Points is

https://community.atlassian.com/t5/Jira-Software-questions/Story-point-and-story-point-estimate-duplicate-fields/qaq-p/904742