"You can't see this item" on my Project

[ayo-run]

What could this possibly be, and how can I remove it? I can't open it. 🥲

[jfullstackdev]

I'm seeing the same thing

would that be related to private repos ? maybe you're not seeing them when not logged-in

[ayo-run]

I'm logged in and I can see all my private repository issues... Is it possible for others to add an item on my public project?

[jfullstackdev]

maybe using of other services in your projects ? bots ? not very sure of that

[jfullstackdev]

I'll also link the other post once it's confirmed it's the same problem of not seeing the item

[khacminh]

The issue occurs when the user doesn't have permission to access the parent repo of the issue. Unfortunately, only enterprise subscription organizations can create fine-grained permission that allows users to read/create issues without access to the source code.
Another (silly) workaround is creating another issue-only repo beside the private source code repo.

I don't know why GitHub doesn't have static reporter permission.

[ossanna16]

Hey there @ayoayco and thank you for asking a good question! I'm glad you found our community 🙂

[tim-bezhashvyly]

For me this happened for the repo I have deleted. So its ticket has been assigned to the board and perfectly visible but after the deletion turned into "You can't see this item". No idea how to remove it.

[md84419]

I've seen this today with a project to which I've been added. I'm in a different organisation to the project owner.

The workaround is to put the following into the filter: "is:open,closed".

Also see #8550. As @dustingoodman has suggested, maybe tickets can have an internal state (such as deleted or orphaned) which isn't exposed through the filter as a TYPE or STATE, and the filter logic isn't filtering them out correctly? https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects#filtering-for-item-state-or-item-type

[tim-bezhashvyly]

Cool. You can also save the filter so it stays default. Thank you for a workaround.