This is where a junior developer can really help, even if it's junior in the sense that they are not as familiar with the project as you are. There is no better

This is where a junior developer can really help, even if it's junior in the sense that they are not as familiar with the project as you are. There is no better way to become familiar with the true problems and priorities of a project than to triage bug reports from the people actually using the software. You may be too deep into it to see that. Don't prioritize based on what is the "fun technical challenge" but instead figure out how you can get users to be happier with what you are building. Also remember that sometimes the answer is code, and quite often it is documentation or a code sample showing the "right" way to do it.