How to find out which are genuine issues to solve?

[prakharsingh-74]

The Issues tab has a lot of open issues, and I'm finding it hard to get to know which ones are genuine and actually approved by the Plane team for an contributor to work on. How do I identify those? Is there a specific label, a maintainer comment, or a process I should look for before I start working on an issue and open a PR?

I want to avoid picking issues the team hasn't confirmed and wasting their review time. Any guidance would really help. Thank you!

[ryavee]

Hi @prakharsingh-74 ,
I think here, I wouldn’t assume that every open issue is ready to be worked on right away.

I think it’s better to first check whether the issue has enough information to understand or reproduce the problem, and whether there’s any indication from the maintainers that they’re open to someone working on it.

For feature requests, Plane’s contribution guide suggests creating an issue with your proposal first and waiting for the team to confirm it before starting the implementation.

For bugs, make sure there’s a clear and reproducible scenario. Plane also recommends providing a minimal reproduction when reporting or fixing bugs.

[prakharsingh-74]

Thanks for your letting me know @ryavee