Could we restrict Story Points to Integers?

[arama mihai]

Hello,

Currently, the Story Points field in JIRA allows values like: 3.5, 0.5, 2.9, (non integers).  

We would like that only integer values should be used. 

And if possible, even just certain integer values: 0,1,2,3,5,8,13,20,40,100. 

Please let me know if this is possible.

Thank you!

[Nic Brough -Adaptavist-]

As the others have mentioned, you will need ScriptRunner or some other form of automation to do this.

You could do it with validators, but you are likely to find "I can't move my issue until I've edited and then changed something to match" is quite annoying for your users.

I would try:

• Create a select list to be used as the fixed list of values.
• Remove "story points" from the edit screens
• Write a numeric scripted field that takes either
• A matching number from the select list
• The original Story points field if the select is not set (this stops you from making existing data invalid)
• Set your estimation to use the scripted field

[Lucy Dilts]

What would be the sql for creating a custom table in jira to store story points as integer..

[Nic Brough -Adaptavist-]

Hi Lucy,

You don't create tables in the Jira database, nor even in the UI.  You would need to find or write an app that can provide a new type of issue field, one that can validate and accept only integers.

[Lucy Dilts]

Hi Nick -

This is not true. You absolutely can create custom tables through analytics in Jira.

I was just looking for the sql syntax that would need to include field id (fk), name and value, where the value would be cast as type 'integer'.

Not difficult to do, just thought someone might have it handy. 

[Nic Brough -Adaptavist-]

I was talking about database tables, as implied by your question, not analytics tables.

I was also talking about fields, where Jira does not have an integer type field.

[Lucy Dilts]

It wasn't implied at all.

Wrote the sql and it works, so all good.

Have now extended the ability to max / min variances in story points. 

I will post the sql in another thread.

[Nic Brough -Adaptavist-]

You should never write anything to a Jira database.  Please don't do that, you will break it.

[Gregor Kasmann_Actonic]

Some Custom Listener may assist you to round Story Point on each issue update. It may be implemented in ScriptRunner or PowerScripts.

[arama mihai]

Thank you, we were just thinking about that. Would you happen to know if something like this might have an impact on JIRA's performance, considering that Story Points is a field used in every issue (except sub-tasks)?

Thank you.

[Gregor Kasmann_Actonic]

You should define the scope properly - Project, Issue Type. Otherwise it may affect performance on huge instances.

[arama mihai]

Thanks, for us it would be all projects eventually, all issue types (except sub-tasks) :(

[Joe Pitt]

No, not out of the box. You may be able to use a script to do it behind the scenes. 

[arama mihai]

Hello,

Thank you for your reply.

Could you be a little bit more precise about the scripts? I was thinking Scriptrunner validators, but those would apply only on transitions, not also on the "Edit" issue event.

Did you have other scripts in mind?

Thank you.

[Joe Pitt]

I don't use them so I can't comment. I often end up installing JIRA on systems that others will manage. Using scripts complicates matters and not all admins have programming experience. From other questions I know scripting can be used to limit data input. I suggest you search for forum and google for something like: JIRA scrips limiting input

[Gregor Kasmann_Actonic]

You can create a custom field (Select List) with predefined values (0,1,2,3,5,8,13,20,40,100). It will be not as useful as default Story Points but users will not be able to put any value in it. And it will be easy to filter it by JQL.

[arama mihai]

Hi,

Thanks, but we would prefer to use the same field so as to not lose other functionality that's specific to the original field.