Fields for issues

[LeaVerou]

Select Topic Area

Product Feedback

Feature Area

Issues

Body

I was so giddy to discover custom fields for projects that allow to assign priority, effort, etc to issues for a given project. I would literally not shut up about it to everyone who would listen 😁

However, my enthusiasm waned once I realized that these a project-specific: assigning a priority or effort level to an issue in one project, means this metadata will not be visible in any way on this issue outside of said project.
So we went back to our existing workaround of just using labels with colons. It can get quite messy, e.g. real example:

I guess a workaround might be to include ALL issues in a project, but that seems very hard to wrangle.

While being able to scope fields to the project is useful, I wonder if it's an edge case. E.g. how likely is an issue to be high effort for one project and low effort for another? Or high priority for one project and low priority for another?

It would be great to support the same fields infrastructure for issues as well, for fields that genuinely intrinsically belong to the issue itself, and not to the Issue-Project relation. The UI is already there, and works great, so hopefully this shouldn't need a ton of effort to do? Perhaps it could even implement the workaround I mentioned above behind the scenes until the infrastructure is there, then it just becomes largely a matter of doing the UI work to hide that.

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. ⭐