First-class support for issue size

[mumrah]

Would be very nice for would-be Agile projects to include a numeric size/estimate field on issues. It could be implemented similarly to labels where you configure a set of sizes with a numeric value and an optional label/color. E.g.,

• 1 "Tiny"
• 2 "Small"
• 3 "Medium"
• 5 "Large"
• 8 "X-Large"

Or

• 1 "★☆☆☆"
• 2 "★★☆☆"
• 3 "★★★☆"
• 4 "★★★★"

Etc

One thing is for sure, you won't make everyone happy if you predefine the possible sizes (everyone has their own preferences), so it would need to be configurable. Some people won't want (or care) about the numeric value, in which case it should just be sequential. But some folks will want Fibonacci, some powers of 2, etc.

The reason I suggest a numeric value in addition to a label is so the task-list progress bar and the milestone progress bar could reflect progress in terms of cumulative issue size (and not just count). For large projects this would allow a more accurate view of "how close X is to being done", and would make many PMs happy

[cirosantilli]

Another possibility is arbitrary key / pair metadata a la. Would also solve the analogous "issue importance" (vs difficulty) use case.

[sergiodosreisjr]

It would be perfect! To complement, I think that the sum of the size of the issues can be included in the title of the columns of the projects, as the example of the image below. Is there any forecast for this implementation?

[bbottema]

My project now indicates it's almost done (only X issues left of Y), but those last issues are greater than all other issues together. The project's progress indicator currently is completely useless.

[CraigLager]

+1 - GitHubs issues are really missing this

[mgiachetti]

I create this chrome extension until this feature is released and made it's open source.
I'm already using it for my plannings.

[DrewWeth]

Can we get an update on this? This has been labeled a priority for almost 2 years.