Version: (using Devel) Installed from: Compiled sources I was wondering if it would be possible to show a component specific message sometime during the report workflow. In KPat there a couple of easy things the reporter can do to greatly increase the chance of their bug being addressed. One is to mention which of the 12 different game types the issue occurred in. About one in three reporters forgets this rather crucial information. The other is to attach a saved game that demonstrates the problem. People often attach screenshots showing a problem with the solver, but we developers can't load up a screenshot to recreate the issue. Omitting these things often leads to at least one step of back and forth to (hopefully) get the information we need. Getting the game type is easy, but getting them to reproduce the issue to make a saved game after they've closed KPat can be tricky. Neither of these is a big deal and I'm sure reporters would gladly do them, if only they new they should. I'm guessing that other components have similar instructions they'd like to share. Integration with Dr. Konqui would also be handy. Maybe if KDevelop was getting dozens of duplicate reports, they could temporarily add a line to their instructions asking people not to report that particular issue.
I believe it is possible, especially since i'm getting ready to simplify the workflow a bit.
Has anyone considered this any further? Considering all the changes going on at bugs.kde.org, it seems like now might be a good time to integrate it.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
This is possible; please file sysadmin tickets at https://phabricator.kde.org/maniphest/task/edit/form/2/ with the product-specific templates you would like to request.