We are working on bug fixes, but no story value assigned for a bug, what is the sprint alternative?

[Deleted user]

I see that the story board values are assigned based on each function rather than each ticket. What if any is an effective way to manage the sprint w/o actual estimates.  Maybe just a high,medium, or low value such as  6, 3, 1.

[Earl McCutcheon]

Hello @[deleted] ,

Check out the following Blog post we have on recommendations surrounding agile estimation relating to story points that touches on a recommendation for setting this up:

• Story points and estimation 

Particularly under the section "Story points vs. hours" noting the following:

Traditional software teams give estimates in a time format: days, weeks, months. Many agile teams, however, have transitioned to story points. Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. It may sound counter-intuitive, but that abstraction is actually helpful because it pushes the team to make tougher decisions around the difficulty of work. Here are few reasons to use story points:

Regards,
Earl

[John Ritchey]

Is there a way to limit Jira Story Points to those in the Fibonacci-sequence?

[Earl McCutcheon]

Hello @John Ritchey ,

The Maximum value allowed in the story point field is capped really high at a value of '100000000000000', which can be seen in an error displayed if you attempt to overload the field:

However I would highly recomend against against going this high as it would become harder to manage as you get to abstract in the sequence, and it is better for tracking to break down the values to smaller pieces for more accurate estimation, as described in the Blog.

Regards,
Earl