Re: Bugzilla template problems
Thanks! On zondag 28 oktober 2018 06:02:13 CET Andrew Crouthamel wrote: > FYI boud, I finally got around to making the changes we agreed to a few > weeks ago: https://phabricator.kde.org/D16474 > > Hopefully that helps. > > > Andrew Crouthamel > > ‐‐‐ Original Message ‐‐‐ > > On Tuesday, October 23, 2018 4:49 PM, Boudewijn Rempt wrote: > > On maandag 8 oktober 2018 21:10:44 CEST Andrew Crouthamel wrote: > > > If someone doesn't want to fill out everything, they don't have to. I've > > > seen plenty of people deleting some of the template or not filling out > > > some > > > fields. > > > > There's another problem: the template assumes people are using Plasma. > > > > SOFTWARE VERSIONS > > (available in About System) > > KDE Plasma Version: > > KDE Frameworks Version: > > Qt Version: > > > > Over half of bug reports for Krita at least are not even from Linux users, > > and many Linux users don't use plasma. Without more explanation (like, If > > you use the KDE Plasma desktop, please...), this part just confuses > > people like heck. Here's where Krita's bug reports came from in the past > > 12 months: > > > > Windows: 683 > > linux: 646 > > macOS: 132 > > > > -- > > -- > > -- > > -- > > -- > > -- > > -- > > > > https://www.valdyas.org | https://www.krita.org -- https://www.valdyas.org | https://www.krita.org
Re: Bugzilla template problems
FYI boud, I finally got around to making the changes we agreed to a few weeks ago: https://phabricator.kde.org/D16474 Hopefully that helps. Andrew Crouthamel ‐‐‐ Original Message ‐‐‐ On Tuesday, October 23, 2018 4:49 PM, Boudewijn Rempt wrote: > On maandag 8 oktober 2018 21:10:44 CEST Andrew Crouthamel wrote: > > > If someone doesn't want to fill out everything, they don't have to. I've > > seen plenty of people deleting some of the template or not filling out some > > fields. > > There's another problem: the template assumes people are using Plasma. > > SOFTWARE VERSIONS > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > Over half of bug reports for Krita at least are not even from Linux users, and > many Linux users don't use plasma. Without more explanation (like, If you use > the KDE Plasma desktop, please...), this part just confuses people like heck. > Here's where Krita's bug reports came from in the past 12 months: > > Windows: 683 > linux: 646 > macOS: 132 > > -- > > https://www.valdyas.org | https://www.krita.org
Re: Bugzilla template problems
On Wed, Oct 24, 2018 at 10:01 AM Nate Graham wrote: > > From the perspective of someone who triages non-Krita bugs, I would say that > the template has been a big success. My observations (again, for non-Krita > bugs) are as follows: > > 1. Technically adept users are now filing better bugs, because they are > faithfully filling out the template with useful information. > > 2. Users with moderate technical and reading comprehension skills are filing > better bugs, because the template is guiding them through the process in a > way that's helpful. > > 3. Users with low technical or reading comprehension skills are still filing > un-actionable bugs, because they are ignoring the template (e.g. > https://bugs.kde.org/show_bug.cgi?id=400150). But they were already filing > useless bugs before; the bugs are just useless in a different way now. > > I understand that this has not been the experience for Krita's bug triagers > because parts of the template assumes Plasma, and perhaps Krita has a > larger-than-average percentage of users who fall under category 3. What this > really suggests to me is that we need per-product templates. If one size does > not fit all, let's try to make it flexible. This could be a huge win for > well-triaged products like Krita since you guys usually know exactly what > information you want to ask bug submitter, and you can tweak your > Krita-specific template until you find that it substantially improves the > situation handling bugs from group #3. It'll also be a massive maintainability issue. Given that quite a bit of the pain at the moment seems to be Platform specific variations, could we try splitting it by Windows / MacOS / Linux before following the path of wanting to partition it per product? (Determining whether they're Plasma, GNOME or something else users might be a bit difficult, but those users should hopefully be aware of the different desktop environments) > > Nate Cheers, Ben > > > > On Tue, 23 Oct 2018 14:49:53 -0600 Boudewijn Rempt > wrote > > On maandag 8 oktober 2018 21:10:44 CEST Andrew Crouthamel wrote: > > > > > > If someone doesn't want to fill out everything, they don't have to. I've > > > seen plenty of people deleting some of the template or not filling out > some > > > fields. > > > > > > > There's another problem: the template assumes people are using Plasma. > > > > SOFTWARE VERSIONS > > (available in About System) > > KDE Plasma Version: > > KDE Frameworks Version: > > Qt Version: > > > > Over half of bug reports for Krita at least are not even from Linux users, > and > > many Linux users don't use plasma. Without more explanation (like, If you > use > > the KDE Plasma desktop, please...), this part just confuses people like > heck. > > Here's where Krita's bug reports came from in the past 12 months: > > > > Windows: 683 > > linux: 646 > > macOS: 132 > > > > -- > > https://www.valdyas.org | https://www.krita.org > > > > > > > >
Re: Bugzilla template problems
On dinsdag 23 oktober 2018 23:01:21 CEST Nate Graham wrote: > I understand that this has not been the experience for Krita's bug triagers > because parts of the template assumes Plasma, and perhaps Krita has a > larger-than-average percentage of users who fall under category 3. What > this really suggests to me is that we need per-product templates. If one > size does not fit all, let's try to make it flexible. This could be a huge > win for well-triaged products like Krita since you guys usually know > exactly what information you want to ask bug submitter, and you can tweak > your Krita-specific template until you find that it substantially improves > the situation handling bugs from group #3. Yes, that would be the only solution: the current solution basically assumes everyone is using the Plasma desktop, and that's just not true. If we cannot have per-product templates, then the template should be much more explicit about which parts are relevant in which situation. You can be as computer literate as possible, but if you're using Windows, instructions to look up the KDE plasma (what is plasma? it doesn't even add 'desktop') version using the "About System" (how to access that?) just don't make any sense. And that's already over half of Krita's bug reporters. And of course, we've got lots of illiterate bug reporters as well, and I'm working on a mail to start a discussion on how we should have to deal with those, but until we've got something else than bugzilla for people to report problems, we need something that helps the illiterate, instead of making them do useless work. That's a waste of time for the reporter and for the maintainer. -- https://www.valdyas.org | https://www.krita.org
Re: Bugzilla template problems
>From the perspective of someone who triages non-Krita bugs, I would say that >the template has been a big success. My observations (again, for non-Krita >bugs) are as follows: 1. Technically adept users are now filing better bugs, because they are faithfully filling out the template with useful information. 2. Users with moderate technical and reading comprehension skills are filing better bugs, because the template is guiding them through the process in a way that's helpful. 3. Users with low technical or reading comprehension skills are still filing un-actionable bugs, because they are ignoring the template (e.g. https://bugs.kde.org/show_bug.cgi?id=400150). But they were already filing useless bugs before; the bugs are just useless in a different way now. I understand that this has not been the experience for Krita's bug triagers because parts of the template assumes Plasma, and perhaps Krita has a larger-than-average percentage of users who fall under category 3. What this really suggests to me is that we need per-product templates. If one size does not fit all, let's try to make it flexible. This could be a huge win for well-triaged products like Krita since you guys usually know exactly what information you want to ask bug submitter, and you can tweak your Krita-specific template until you find that it substantially improves the situation handling bugs from group #3. Nate On Tue, 23 Oct 2018 14:49:53 -0600 Boudewijn Rempt wrote > On maandag 8 oktober 2018 21:10:44 CEST Andrew Crouthamel wrote: > > > > If someone doesn't want to fill out everything, they don't have to. I've > > seen plenty of people deleting some of the template or not filling out > > some > > fields. > > > > There's another problem: the template assumes people are using Plasma. > > SOFTWARE VERSIONS > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > Over half of bug reports for Krita at least are not even from Linux users, > and > many Linux users don't use plasma. Without more explanation (like, If you > use > the KDE Plasma desktop, please...), this part just confuses people like > heck. > Here's where Krita's bug reports came from in the past 12 months: > > Windows: 683 > linux: 646 > macOS: 132 > > -- > https://www.valdyas.org | https://www.krita.org > > >
Re: Bugzilla template problems
On maandag 8 oktober 2018 21:10:44 CEST Andrew Crouthamel wrote: > > If someone doesn't want to fill out everything, they don't have to. I've > seen plenty of people deleting some of the template or not filling out some > fields. > There's another problem: the template assumes people are using Plasma. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Over half of bug reports for Krita at least are not even from Linux users, and many Linux users don't use plasma. Without more explanation (like, If you use the KDE Plasma desktop, please...), this part just confuses people like heck. Here's where Krita's bug reports came from in the past 12 months: Windows: 683 linux: 646 macOS: 132 -- https://www.valdyas.org | https://www.krita.org
Re: Bugzilla template problems
On maandag 8 oktober 2018 21:10:44 CEST Andrew Crouthamel wrote: > > We had this previously, where the details were added in without any template > and the bug reports were very lacking, always requiring follow-up work. The > current template is at least producing bugs with higher quality > information. Um, I'm not convinced of that. Since we've gotten the new template, I'm getting quite a few bugs like https://bugs.kde.org/show_bug.cgi?id=400218 -- though I cannot imagine how the system info got into the subject, it's only one of the bugs I've seen recently where the summary isn't filled in at all. -- https://www.valdyas.org | https://www.krita.org
Re: Bugzilla template problems
‐‐‐ Original Message ‐‐‐ On Friday, October 5, 2018 2:23 PM, Karl Ove Hufthammer wrote: > BTW, is having to enter detailed metainfo in Bugzilla really > neccesary? Currently, even for simple bugs, I have to enter: [...] > > As a comparison, at GitHub, to file a bug, you just have to enter: > > Title > Description > We had this previously, where the details were added in without any template and the bug reports were very lacking, always requiring follow-up work. The current template is at least producing bugs with higher quality information. If someone doesn't want to fill out everything, they don't have to. I've seen plenty of people deleting some of the template or not filling out some fields. Andrew Crouthamel
Re: Bugzilla template problems
Kai Uwe Broulik skreiv 05.10.2018 09:16: I find it odd that you can write meaningful bugreports using DrKonqi that include version information and find the correct component whereas the "Report a bug" in "Help" just opens bugzilla webpage. It does fill out the correct product and version but could surely be improved or turned into a proper wizard with some tips and tricks and duplicate finder and what not. And perhaps have it work for the ‘System Settings’ modules too? It’s such a pain to find the correct components (which have cryptic names, like ‘kcm_kdnssd’) (pop quiz: what’s the correct component for the ‘Display and Monitor’ module?). Or just right-clicking on an icon on the task bar (or in an application launcher) and select ‘Report Bug...’? BTW, is having to enter detailed metainfo in Bugzilla *really* neccesary? Currently, even for simple bugs, I have to enter: Product Component Version Severity Platform OS Summary Description KDE Plasma Version KDE Frameworks Version Qt Version That’s a pretty high bar for bug reporting, e.g. when you just want to just report a simple typo. And when *editing* an existing bug report, you have these additional fields: Status Alias Importance Target Milestone Assignee URL Keywords Personal Tags Depends on Blocks Latest Commit Version Fixed In Flags As a comparison, at GitHub, to file a bug, you just have to enter: Title Description And it seems to work fine. Sure, *sometimes* the Platform (openSUSE-specific bugs) or OS (Windows) is relevant, but then you’ll typically mention it in the actual description (or just ask the reporter), but *typically* it’s of no use. The same is true for the Version. And the 8-level Severity rating is usually completely ignored (perhaps except for ‘critical’ severity). So couldn’t Bugzilla be simplified so that we only ask for information on a ‘need to know’ basis? -- Regards, Karl Ove Hufthammer
Re: Bugzilla template problems
I do have a task on my to-do list for improving this using the new API we can use nowadays. So, it's possible to make this lots better and just needs coding really. If anyone wants to try I can mentor or give emotional support :) On Fri, Oct 5, 2018, 09:16 Kai Uwe Broulik wrote: > Am 04.10.2018 um 22:11 schrieb Harald Sitter: > > Oh btw, just as a random FYI: I think stuff like this is why ubuntu > > eventually ended up having a GUI tool (ubuntu-bug) to help file bug > > reports with useful metadata. Putting it on the user to figure this > > stuff out is unreliable at best and can easily get overwhelming. > > > > +1 > I find it odd that you can write meaningful bugreports using DrKonqi > that include version information and find the correct component whereas > the "Report a bug" in "Help" just opens bugzilla webpage. > > It does fill out the correct product and version but could surely be > improved or turned into a proper wizard with some tips and tricks and > duplicate finder and what not. >
Re: Bugzilla template problems
Am 04.10.2018 um 22:11 schrieb Harald Sitter: Oh btw, just as a random FYI: I think stuff like this is why ubuntu eventually ended up having a GUI tool (ubuntu-bug) to help file bug reports with useful metadata. Putting it on the user to figure this stuff out is unreliable at best and can easily get overwhelming. +1 I find it odd that you can write meaningful bugreports using DrKonqi that include version information and find the correct component whereas the "Report a bug" in "Help" just opens bugzilla webpage. It does fill out the correct product and version but could surely be improved or turned into a proper wizard with some tips and tricks and duplicate finder and what not.
Re: Bugzilla template problems
On Fri, Oct 5, 2018 at 10:27 AM Valorie Zimmerman wrote: > > On Thu, Oct 4, 2018 at 1:11 PM Harald Sitter wrote: >> >> Oh btw, just as a random FYI: I think stuff like this is why ubuntu >> eventually ended up having a GUI tool (ubuntu-bug) to help file bug >> reports with useful metadata. Putting it on the user to figure this >> stuff out is unreliable at best and can easily get overwhelming. > > > This. Is there a way for us to have the Help > File a bug menu start a > "kde-bug" process like "ubuntu-bug" ? And to have a `kde-bug packagename` in > the commandline? In Kubuntu, this makes filing even complex bug reports (such > as against the installer while testing release candidate ISOs) much more > easy, and the information provided is exactly what the Ubuntu developers need > to make fixes. Currently all we have is the following class in KXMLGUI: https://lxr.kde.org/source/frameworks/kxmlgui/src/kbugreport.cpp > > Valorie > Cheers, Ben > -- > http://about.me/valoriez > >
Re: Bugzilla template problems
On Fri, Oct 5, 2018 at 9:07 AM Harald Sitter wrote: > > On Thu, Oct 4, 2018 at 6:14 PM Nate Graham wrote: > > > > Can the template be overridden on a per-project basis? > > Yes. > > [% IF product.name == 'foobar' %] > ... > [% END %] > > I think making the template text more generically applicable is more > reasonable though. Otherwise the about system bit can basically only > be shown for plasma products as everything else may very well have > (more) !plasma based users than plasma based ones. Also, adding > per-project conditionals in the template is probably going to get a > maintenance burden quickly. I would very much rather prefer we avoid per-project templates as that's definitely inviting a maintainability nightmare. > > Reference of the template language for prosperity: > http://www.template-toolkit.org/docs/manual/index.html > > HS Cheers, Ben
Re: Bugzilla template problems
On Thu, Oct 4, 2018 at 1:11 PM Harald Sitter wrote: > Oh btw, just as a random FYI: I think stuff like this is why ubuntu > eventually ended up having a GUI tool (ubuntu-bug) to help file bug > reports with useful metadata. Putting it on the user to figure this > stuff out is unreliable at best and can easily get overwhelming. > This. Is there a way for us to have the Help > File a bug menu start a "kde-bug" process like "ubuntu-bug" ? And to have a `kde-bug packagename` in the commandline? In Kubuntu, this makes filing even complex bug reports (such as against the installer while testing release candidate ISOs) much more easy, and the information provided is exactly what the Ubuntu developers need to make fixes. Valorie -- http://about.me/valoriez
Re: Bugzilla template problems
Oh btw, just as a random FYI: I think stuff like this is why ubuntu eventually ended up having a GUI tool (ubuntu-bug) to help file bug reports with useful metadata. Putting it on the user to figure this stuff out is unreliable at best and can easily get overwhelming.
Re: Bugzilla template problems
On Thu, Oct 4, 2018 at 6:14 PM Nate Graham wrote: > > Can the template be overridden on a per-project basis? Yes. [% IF product.name == 'foobar' %] ... [% END %] I think making the template text more generically applicable is more reasonable though. Otherwise the about system bit can basically only be shown for plasma products as everything else may very well have (more) !plasma based users than plasma based ones. Also, adding per-project conditionals in the template is probably going to get a maintenance burden quickly. Reference of the template language for prosperity: http://www.template-toolkit.org/docs/manual/index.html HS
Re: Bugzilla template problems
On Thu, 4 Oct 2018 at 21:06, Boudewijn Rempt wrote: > On donderdag 4 oktober 2018 21:01:37 CEST Jaroslaw Staniek wrote: > > So I would imagine that quite general approach would be to allow "None" > > value for Plasma version and even KF5 version (this covers non-KF5 apps). > > "None" in contrast to "Unknown". > > That's not relevant. It isn't a matter of what's allowed or not; this is a > plain text thing people are supposed to understand and maybe fill in. > There > are no canned answers, no comboboxes, no help for the user. > > > PS: What's the link to the template please? > > Just go to bugzilla, try to enter a new bug and look at what's pre-filled > in > the report field. > Ah textual template! Thanks Boud. I propose approach like below; one size fits all since the product can be even non-Qt one (or built as non-Qt or non-KF5 or be entirely non-C++). Saying "SYSTEM SOFTWARE VERSIONS" helps to avoid cases when user repeats the app's version. -- BEFORE: SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: --8x--- -- AFTER: SYSTEM SOFTWARE VERSIONS 1. Operating system version: 2. Click "Help menu->About app->Libraries" and provide: * KDE Frameworks Version (KF5): * Qt Version: Skip if unused. Alternatively type "kf5-config --version" or "qmake-qt5 --version" from the command line. * KDE Plasma Version: Skip if unused. Alternatively type "plasmashell --version" from the command line. --8x--- Also: Why Android has versions in the OS field? Moreover I see room for improvement for KF5-based apps in the command line. The --version option does not show Qt nor KF5 version. In contrast Creator shows Qt version. IIRC "KDE4" apps used to show Qt and KDE platform 4 versions (just checked with KDevelop). Maybe this is reported already, nevertheless can be a good junior/season job. When this gets fixed the "kf5-config --version" / "qmake-qt5 --version" / "plasmashell --version" usually won't be needed, just "appname --version", at least for KF5 apps. Related: In project where I contribute I am quite picky about showing as much as possible of version info, also found plugins and their versions. This so often helps to figure out potential issues. Also this way users do not need to discover OS-dependent way of discovering plugins/dependency versions (can be funny on Windows). -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Bugzilla template problems
On donderdag 4 oktober 2018 21:01:37 CEST Jaroslaw Staniek wrote: > So I would imagine that quite general approach would be to allow "None" > value for Plasma version and even KF5 version (this covers non-KF5 apps). > "None" in contrast to "Unknown". That's not relevant. It isn't a matter of what's allowed or not; this is a plain text thing people are supposed to understand and maybe fill in. There are no canned answers, no comboboxes, no help for the user. > PS: What's the link to the template please? Just go to bugzilla, try to enter a new bug and look at what's pre-filled in the report field. -- https://www.valdyas.org | https://www.krita.org
Re: Bugzilla template problems
So I would imagine that quite general approach would be to allow "None" value for Plasma version and even KF5 version (this covers non-KF5 apps). "None" in contrast to "Unknown". PS: What's the link to the template please? On Thu, 4 Oct 2018 at 19:27, Ben Cooksley wrote: > On Fri, Oct 5, 2018 at 5:14 AM Nate Graham wrote: > > > > Can the template be overridden on a per-project basis? > > It cannot be overridden on a per-project basis from my understanding. > > Regards, > Ben > > > > > Nate > > > > > > On 10/04/2018 07:48 AM, Boudewijn Rempt wrote: > > > Hi, > > > > > > This section: > > > > > > SOFTWARE VERSIONS > > > (available in About System) > > > KDE Plasma Version: > > > KDE Frameworks Version: > > > Qt Version: > > > > > > In the template I've never seen filled out. One problem, of course, is > that > > > it's really plasma centric. Most of my users don't use plasma, and > don't have > > > an "About System" app that shows this information. Is there are a way > to > > > reformulate this so we won't confuse our users? > > > > > > -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org KEXI: : A visual database apps builder - http://calligra.org/kexi http://twitter.com/kexi_project https://facebook.com/kexi.project Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
Re: Bugzilla template problems
On Fri, Oct 5, 2018 at 5:14 AM Nate Graham wrote: > > Can the template be overridden on a per-project basis? It cannot be overridden on a per-project basis from my understanding. Regards, Ben > > Nate > > > On 10/04/2018 07:48 AM, Boudewijn Rempt wrote: > > Hi, > > > > This section: > > > > SOFTWARE VERSIONS > > (available in About System) > > KDE Plasma Version: > > KDE Frameworks Version: > > Qt Version: > > > > In the template I've never seen filled out. One problem, of course, is that > > it's really plasma centric. Most of my users don't use plasma, and don't > > have > > an "About System" app that shows this information. Is there are a way to > > reformulate this so we won't confuse our users? > > >
Re: Bugzilla template problems
Yes, that would be much better. On donderdag 4 oktober 2018 18:19:19 CEST Andrew Crouthamel wrote: > Why not just something generic: > > SOFTWARE/OS VERSIONS > Windows: > MacOS: > Linux/KDE Plasma: > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > Andrew Crouthamel > > ‐‐‐ Original Message ‐‐‐ > > On Thursday, October 4, 2018 12:13 PM, Nate Graham wrote: > > Can the template be overridden on a per-project basis? > > > > Nate > > > > On 10/04/2018 07:48 AM, Boudewijn Rempt wrote: > > > Hi, > > > This section: > > > SOFTWARE VERSIONS > > > (available in About System) > > > KDE Plasma Version: > > > KDE Frameworks Version: > > > Qt Version: > > > In the template I've never seen filled out. One problem, of course, is > > > that > > > it's really plasma centric. Most of my users don't use plasma, and don't > > > have an "About System" app that shows this information. Is there are a > > > way to reformulate this so we won't confuse our users? -- https://www.valdyas.org | https://www.krita.org
Re: Bugzilla template problems
That sounds a lot better. Even on Linux kf5!=plasma . On Thu, Oct 4, 2018, 12:19 PM Andrew Crouthamel wrote: > Why not just something generic: > > SOFTWARE/OS VERSIONS > Windows: > MacOS: > Linux/KDE Plasma: > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > Andrew Crouthamel > > ‐‐‐ Original Message ‐‐‐ > On Thursday, October 4, 2018 12:13 PM, Nate Graham wrote: > > > Can the template be overridden on a per-project basis? > > > > Nate > > > > On 10/04/2018 07:48 AM, Boudewijn Rempt wrote: > > > > > Hi, > > > This section: > > > SOFTWARE VERSIONS > > > (available in About System) > > > KDE Plasma Version: > > > KDE Frameworks Version: > > > Qt Version: > > > In the template I've never seen filled out. One problem, of course, is > that > > > it's really plasma centric. Most of my users don't use plasma, and > don't have > > > an "About System" app that shows this information. Is there are a way > to > > > reformulate this so we won't confuse our users? > > >
Re: Bugzilla template problems
Why not just something generic: SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Andrew Crouthamel ‐‐‐ Original Message ‐‐‐ On Thursday, October 4, 2018 12:13 PM, Nate Graham wrote: > Can the template be overridden on a per-project basis? > > Nate > > On 10/04/2018 07:48 AM, Boudewijn Rempt wrote: > > > Hi, > > This section: > > SOFTWARE VERSIONS > > (available in About System) > > KDE Plasma Version: > > KDE Frameworks Version: > > Qt Version: > > In the template I've never seen filled out. One problem, of course, is that > > it's really plasma centric. Most of my users don't use plasma, and don't > > have > > an "About System" app that shows this information. Is there are a way to > > reformulate this so we won't confuse our users?
Re: Bugzilla template problems
Can the template be overridden on a per-project basis? Nate On 10/04/2018 07:48 AM, Boudewijn Rempt wrote: Hi, This section: SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: In the template I've never seen filled out. One problem, of course, is that it's really plasma centric. Most of my users don't use plasma, and don't have an "About System" app that shows this information. Is there are a way to reformulate this so we won't confuse our users?
