"Numeric Single Select" Field Type

[Grisgram]

Select Topic Area

Product Feedback

Feature Area

Projects

Body

We created a field to enter the story points (SP) of a story during sprint planning.

To avoid having to type the same numbers again and again (and possibly open the gate to typo-world and people ignoring the 1-2-3-5-8-13 Fibonacci pattern), we decided to set the type Single Select.

It looks like this.

This also offered the us a good way to colorize the story size, as you can see above.

However, such a field can not be set to be the Sum of the column, as there are only numeric fields allowed.
Instead of just having the count of items in a column (which can be seen quite clearly in a board showing only the current sprint), we'd like to see the sum of story points there. But this is not possible, due to the field being Single Select.

Create a Numeric Single Select Field Type

If we could've set the field to be a numeric drop down, github would be able to summarize it, increasing the usability of the "Sum" feature greatly while, at the same time, allowing to colorize the entries in the list for a better visual experience.

Thanks for reading!

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[julienlavergne]

I suggest defining two separate concepts: the field type and the allowed values.