Customizing Story Points Field

[Emily Sefcik]

I would like to customize the default Story Points field so that it is a drop down menu following the Fibonacci sequence.

Is there any way to do this? 

It seems the locked Story Points field is the only one that feeds into reporting and displays on the issue cards when viewing all issues in aggregate (for example, in the backlog or in the active sprint). Given that, it seems that creating an additional custom field for Story Points does not have the same impact as using the default locked version. However, I cannot determine any way to make this change on the default story points field. 

[Mikael Sandberg · Accepted solution]

Correct, the story point field is locked. Your only option would be to create your own custom field, just note that Estimations on a board can only be based on a number field, not a select field.

[Emily Sefcik]

Thanks! 

[Thayne Munson]

Thanks. 

[Thomas Kluge]

@Mikael Sandberg, I am trying to achieve this (story points with a drop-down menu) with Jira Cloud. Creating a custom field based on "Number Field" and setting this as estimation statistics is fine, but how to add the drop-down with the preset values to it?
I tried an approach with a Forge custom field type, but this is apparently not accepted as estimation statistics, see also my post here:
https://community.developer.atlassian.com/t/custom-field-to-be-used-as-estimation-statistics/64902

Many thanks for any help!

[Mikael Sandberg]

Hi @Thomas Kluge,

Welcome to Atlassian Community!

This should probably be it's own question and reference this one, but you could do something similar to what @Nic Brough -Adaptavist- mentioned using your Forge script. Another option would be to use automation that copies the value from your drop-down custom field to the story point field.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Estimation fields have to be numeric, it won't work with a select list, even if all the options look like numbers.

[Thomas Kluge]

Thanks, @Mikael Sandberg and @Nic Brough -Adaptavist- !

Got it. My Forge app does provide a custom field type which is numeric, as it uses "number" as the data type. Still it is not available for estimation statistics. Could this be a bug in Jira?

Using two fields, one to enter the value, and another one to display it should work. Looks a bit like a workaround to me, and might confuse users.

[Nic Brough -Adaptavist-]

It might be a bug with the estimate not recognising the field as a number, yes.  I'm not sure though - I don't have an example of a forge app providing a numeric field to play with  and investigate/replicate.

Using two fields can be a pain for the users, but a quick, dirty, and yet helpful trick is to mess with the screens.  Put the select list on create and edit screens, but maybe not view.  Put the calculated one on view, but not create and edit.

[Thomas Kluge]

Nic,

thanks! I ended up solving this as you suggested: one selection field and one hidden number field. Synchronization by an event listener in a Forge app. Still surprising that a workaround is necessary for such a central feature (IMHO).

There is a feature request now for using the custom field type directly:

JRACLOUD-80331 

[Nic Brough -Adaptavist-]

I've solved this with Scriptrunner - you have your "estimate entry" field as a drop-down, then have a scripted field that reads the value from the field and presents it as a number for the estimation statistic.