Team Managed Project - Issue on Story Points

[MJJALP]

We created a new field on a team managed project to limit the story points to certain numbers to select from and not to be a open numerical field.  We called it Story Point Estimation

Course as we review the backlog we see our issue, and it is that the out of the box item for the fields is called "STORY POINTS" (In settings if we remove estimation then it is gone).  Is there a way to fix this in our team managed project?

A) Can I go back and use the STORY POINTS FIELD and limit the data entered (3, 5, 8, 13 and 21 are the values we are going with).  How would I do that?  Then would this automatically go from a story, to the backlog (value of the story points) and be added up for that sprint when I review the backlog?

Can I update the list of fields on the backlog?  (Team managed project). 

Is it better to just create a filter for Issues or List to perhaps use and total up the story points in our new custom field and ignore the story points (Estimate turned off) on the backlog?

Thanks

[Trudy Claspill]

Hello @MJJALP 

Welcome to the Atlassian community.

Can you confirm for us the type of project you are using? Go to the View All Projects page under the Projects menu. Find you project in the list. What does it say in the Type column?

The reason I ask is because the native Story Points field is used only by Company Managed projects. In Team Managed projects the native Story point estimate field is used. If you are truly using a Team Managed project the Story Points field would not have been working but the native Story point estimates field would work.

Only the native story point field will display within the cards on a board; in Company Managed projects that would the the Story Points field and in Team Managed projects that would be the Story point estimate field. 

In Company Managed projects you can add more fields to the card, but you can change which field is referenced in the native story point lozenge. In Team Managed projects you cannot do either.

You cannot limit what can be entered into the native story point fields in either type of project natively. You might be able to add constraints with a third party app like Behaviours from Adaptavitst. Or you can add a Rule to the workflow transitions to check the value in the fields and prevent the transition if it doesn't match one of the acceptable values. Or you can use an Automation Rule to review the value and change it or send a notification to somebody if it is not one of the acceptable values.

[MJJALP]

Team Managed - Now when I go to the backlog  - and see the settings of ESTIMATE is ON - the word STORY POINTS appears when I hover over the amount.    So I think we may have goofed up the field names when we were creating items.  How do I go back and make this work within  - the standard item?  Get rid of our field to force the values and how do I bring back the out of the box field?

[Bill Sheboy]

Hi @MJJALP -- Welcome to the Atlassian Community!

Adding to Trudy's suggestions:

Although Team-managed projects use the "Story Point Estimate" field, it is not consistently called that in the UX.  For example, in the Project Settings where you checked for the estimation type, it is just called "Story Points".  On the issue views, it has the correct field name.

Kind regards,
Bill