SUMMARY In the "Open bugs reported by me" link on the homepage, it does not show bugs that are marked as "NEEDSINFO" (or maybe it's "WAITINGFORINFO" that makes it not show up? I'm not sure). This may be intentional but to me it makes more sense to list these, as it makes it easier to find the bug again and give that requested information. There may certainly be other labels here that cause bugs to not show up, even when there is a follow-up response expected from the reporter. This change could prevent bugs from getting lost in a reporter's list of bugs. I currently have several 18 open bug reports, usually with a few getting active engagement at any given time. It can be easy for reports that don't show up this "Open bugs" list to be forgotten about, which I'm sure is frustrating for the maintainers that take time to review the reports and have asked for information to help fix a problem! Email notifications are sent out, but these are for all bugs that a user is CC'd on, which means if they have several (including closed issues that may get bumped), it may not be reasonable for emails to be how they keep on top of bugs. STEPS TO REPRODUCE 1. Sign into https://bugs.kde.org/ 2. Click on the "Open bugs" list 3. If you have a bug marked as "NEEDSINFO" / "WAITINGFORINFO", it won't be displayed OBSERVED RESULT Bugs marked as "NEEDSINFO" / "WAITINGFORINFO" do not appear in the "Open bugs reported by me" page. EXPECTED RESULT Bugs marked as "NEEDSINFO" / "WAITINGFORINFO" should show up in the "Open bugs reported by me", as they are still open but just pending more information from the reporter, who may forget more easily if it's not in the open bugs list.
Of course I notice this after reporting, but there is a link on the bottom of the "Open bugs reported by me" page that says "My Bugs", and this page lists the bugs that are marked with NEEDSINFO / WAITINGFORINFO However I still think having this be the *default* makes a bit more sense, for the reasons I outlined.
Technically "NEEDSINFO" is a closed status, not an open status. This is an implementation detail that's not obvious, of course. But, as you observed, there is already a way to see your bugs including these. So I think that's enough.