Feature request: Smoothing the Projects adoption with reflecting the implicit issue statuses

[ufukty]

Select Topic Area

Product Feedback

Feature Area

Projects

Body

Current behavior

After creating a project on a repository for the first time and imported all the existing issues into the Project; GitHub presented all with no-status state expected me to manually assign current statuses for each issue among backlog, ready, in-progress, etc.

Proposed behavior

GitHub to calculate and assign the current status of each issue based on the issue having:

• a PR attached with a closing keyword,
• another open related issue (attached with B + B as blocking issue or other)

Such improvement would make the Projects feature adoption far smoother and actually impactful.

Related

Searched for the keywords "closing", "sync" and "status". There is not exact match for one-to-one, fully automated issue status reflection on the Projects view feature request.

• Add default workflows for PR draft and ready-for-review status changes in Projects #159684 wants the ability to set workflows for assigning issue status triggered with PR status activity..
• [Projects Beta] Issues linked in PR do not follow PR status #6339 wants associated issues to follow PR status update.

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