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

I’m having the same problem; I hope it’s just a bug and that it will be fixed soon!

Our team is seeing the same problem. We can access these controls from columns in tabbed views, so I, too, am hopeful this change is simply a bug. The input box under projects was the easiest way to manage issues from other repos in the same project.

Hi - We are also experiencing the same issue - https://github.com/orgs/community/discussions/183897

I can reproduce this consistently. The issue belongs to a repo owned by one account, and the project is a user project owned by another account.

Steps

1. As alice, create a user project: alice/projects/1.
2. Add an issue from a repo owned by someone else, e.g. acme/widgets#42 (alice has access to the repo).
3. Open https://github.com/acme/widgets/issues/42.

What happens

The "Projects" section in the sidebar shows alice/projects/1 for a split second, then it disappears and shows "None yet".

The item is still in the project. It shows on the board, and the "Item closed" workflow still moves it to Done when the issue is closed.

What the API returns

Same issue, same token:

query {
  repository(owner: "acme", name: "widgets") {
    issue(number: 42) {
      projectsV2(first: 10) { nodes { title } }
      projectItems(first: 10) { nodes { project { title } } }
    }
  }
}

• projectsV2 → returns alice/projects/1
• projectItems → empty

When the repo and the project have the same owner (e.g. alice/tool#1 in alice/projects/1), both fields return the project and the sidebar shows it.

The inconsistency

The two fields disagree about the same link. The sidebar seems to render once from data that includes the project, then re-render from data that filters it out. Either both should include cross-owner projects or both should exclude them. Right now the page flickers between the two answers.

Why I care

I use one private user project to track issues and PRs across repos I don't own (upstream bugs I reported, PRs waiting on maintainers, client repos). The board itself works fine. It's only the issue page that can't show me, and only me, which of my projects the issue is in. A private project should be visible on the issue page to people who can see that project, regardless of who owns the repo.