The application that this site uses is old, limited and malfunctioning when one tries to upload a few screenshots; besides, one cannot edit a comment once published if has made a mistake or remembers some detailes he had forgotten when posting the bug report, or thinks it can be better reprahased, etc, etc. So I'd want to suggest that if it doesn't involve much complication, BKO abandoned this clumsy platform and use Discourse instead, or any other similar, gratis (if you make the installation and hosting by yourself) and open source, I propose Discourse because is the only that I know and I know that it's well tested and mantained and used eficaciuosly by bug report systems and forums like Manjaro's. Mozilla's Twitter's, etc. I guess BKO webmasters already know of it, but in case they dont, please throw an eye on it: https://www.discourse.org/
Discourse is not a bug tracking system.
(In reply to Nicolás Alvarez from comment #1) > Discourse is not a bug tracking system. Indeed. Our long-term plan is to migrate to GitLab issues.
Ah, sorry. I mentioned Discourse because Manjaro uses it as bug tracker (https://forum.manjaro.org/c/manjaro-arm/bug-reports) and was the only that sounded a bit to me, not because I know anything about these matters (besides KDE's bug tracking platform sucks xD). I'm glad to read that you are planning to migrate to a better platform :), even if in a long term...
Also, you mentioned Mozilla also using Discourse, but they created Bugzilla and still use it (more extensively than us).
I'd seen several bug reports like this: https://discourse.mozilla.org/t/localisation-file-bug-in-thunderbird-extension/24276 and I thought Mozilla was using Discourse as a bug tracker. Maybe just some people is using incorrectly Mozilla's Discourse to report bugs and I was mislead by that. Sorry.
I must confirm that Discourse is in no way designed to power bug trackers, and would be quite a downgrade even from bugs.kde.org's current engine. The only engines which I believe would be worth investigating as Bugzilla replacements are Atlassian Jira and Redmine. Please take care to formulate issue reports as reports of *issues*, rather than requests. For example, this ticket should be titled something like "Uses aging engine", not "Migrate to [some engine]". It is fine to suggest specific solutions in your ticket, but that should not be done in its title. Another approach is to instead report specific issues of the current engine. Which is already started; the editing limitation you mention is already tracked in ticket #334299, and I personally already reported a significant number of other bugs.kde.org issues which likely come from its engine.