Filtering issues with no:project is faulty

[tobiasamft]

The ability to filter issues with no:project is faulty.

Some issues without any project assigned are not listed when they had been assigned to a project before.

References:

The bug has been mentioned earlier here: isaacs/github#1291 (comment)

Steps to reproduce:

• Have at least one open project
• Have some open issues which are not assigned to a project
• Go to an issue and assign a project
• Filter issues with no:project -> correct result
• Go to the issue and remove the project
• Filter issues with no:project -> incorrect result
• Go to issue again, assign yourself, clear assignee again
• Filter issues with no:project -> correct result

Step 1: have an open project

Step 2: filter issues with no:project

Step 3: go to issue and assign project

Step 4: filter issues with no:project

Step 5: go to issue and remove project

Step 6: filter issues with no:project -> faulty: issue is missing

Step 7: go to issue again, assign yourself, clear assignee again

Step 8: filter issues with no:project -> issue can be seen again

[hellwolf]

yes, please someone help

[hellwolf]

yes, please someone help

[canalnoises]

It would be really good to get this fixed. We have a repository with ~600 issues and it seems that 29 of them aren't currently assigned to a project. With no:project not working properly we have essentially no way to identify those 29 missing issues.

[randori-ddejohn]

Cannot currently set up an auto-add project workflow because no:project is an invalid field name:

[brandong954]

Still not able to filter ALL issues with no:project. Is this being addressed, or is there a better way to find all issues with no associated project?