We want to use a defined scale for our story points in JIRA. How can I at least change the description therefore?

We use story points to estimate stories. How can I change the configuration of story points? At least the description or translation (it currently is set to "... Grö?e der ..." which should at least be "... Größe der ..." and - better yet - adding information about our scale.

Is there a possibility to restrict entered numbers to the ones we'd like to allow (1..10 / Fiabonacchi / Mountain Goat / ... - there are some possibilities that all have a set of numbers).

Thanks in advance,



3 answers

1 accepted

0 votes
Answer accepted


You can change the description of story points just like any other custom field.


Unfortunately you can't change the field type of custom field after its been created, so story points are an opened ended number field. I also wish I could change this to powers of 2 (1, 2, 4, 8), something that the much less feature rich Pivotal Tracker actually supports.

Well, I experienced difficulties in changig that field that is: changing could be done but afterwards the original description was again shown. I will dig into this again in the next days - had to postpone it to some day in May.

Hi Maud,

That field probably cannot be modified, so my answer may not help much, but here it goes.

I always recommend the modified Fibonacci approach (1,2,3,5,8,13,20,40,100).  Then, you just need to remind your teams of the valid numbers.  If you notice a '4', either have a conversation or make it a 5.

Ideally, each team will have their own definition of 'what a 5 is' so the best way to do any cross-project analysis on performance is converting it to a ratio.  I don't personally have to do that.  

If this is important to you, google Rapid Scrum and view their short presentations.  It is good stuff, just doesn't play well with JIRA at this point.

Hello, yes I also prefer Fibonaccis :-) Regards, Maud

Hi Folks,

I found the solution in misconfigured field schemes. It works now. Thanks for your help.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

626 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you