Can’t change assignee on issues created inside a private project (but works in repo issues)

[8bitdev0x8]

Select Topic Area

Bug

Feature Area

Projects

Body

When creating an issue from inside a GitHub Project (v2) in a private repository, the issue’s assignee can be set at creation time, but cannot be changed afterward. This behavior doesn’t happen when creating issues directly from the repository — only when doing so from inside the Project view.

Steps to reproduce:

1. Create a private repository.
2. Invite a collaborator and give them Write access.
3. Create a Project (v2) under that repo (or linked to it).
4. Open the project and create a new issue from the project’s “+” button.
5. While creating the issue, assign it to someone — works fine.
6. After the issue is created, try to change or remove the assignee from the issue’s sidebar (inside the project).

Notes:

1. This issue only occurs when creating the issue from inside a project view.
2. Works fine when creating directly from the repo’s “Issues” tab.
3. The collaborator can still edit assignees normally on repo-created issues.

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

[grantcurell]

Did you ever get this fixed? This is blindly huge bug and I don't understand how it hasn't come up more. It basically renders projects useless.