Support filter forcing functions for project-level fields

[chicgeek]

Select Topic Area

Product Feedback

Feature Area

Projects

Body

Summary

GitHub Projects should support forcing functions for project-level fields, similar to how Notion databases do. This would improve consistency and automation for teams working at scale without using actions.

It would also mitigate frustration when creating an issue in a view and seeing the "The issue was created but is not visible in this view" message.

Current behaviour

At present, forcing functions work for labels, type, and assignee.

However, this does not work for project-level fields (except label), including status and custom select fields.

Proposed behaviour

Allow users to set forcing function rules for project-level fields. This would align project management in GitHub with the flexibility Notion and other database tools already provide.

Examples

In Notion

From Thomas Frank. The filter requires Seen Recently to be TRUE. New items created with this filter, force the TRUE value for that property.

Forcing-Function.mp4

In Github Projects

Issues created under a view with the filter:

label:"new issue" product:"ABC Foods" status:"Triage" type:Request

Would have the requisite properties added.

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