Allow separate issues tab on forks of a repo?

[ffd8]

Dear Github Team

I just ran into an interesting situation... there's a Processing library for using openCV which has run into issues with Processing's 4.0 beta... a Stackoverflow thread points people to a fork of that library. So at the moment, development is continuing and the community are looking at a fork, which may eventually find it's way to the main project, but in the meantime, there's no way to discuss additional issues/ideas for that person's fix, since the 'issues' tab is missing on a fork. Sorry if this is just unique to this repo/fork and normally it's there.. or have you considered allowing totally separate issues to be written on forks?

Cheers!

[derMart]

Yes, please allow issues on forks. This is one of the main drawbacks of Github at the moment in my opinion. Another scenario is when a project is not maintained anymore (even worse if the project gets archived so issues are read only). A fork then has no option to track its issues, very bad situation, seen a few times already.

[tyler2cr]

+1 for this feature request. It might be a prerequisite for adding support for forks in projects: #14977

[syntaxsdev]

+1 also bump

[sakul-the-one]

+1