GNOME Bugzilla – Bug 742758
Provide on the fly search when entering issue report titles
Last modified: 2015-02-10 21:50:06 UTC
Usually one is more carefully when choosing the title when acutally entering it in the report form than when searching for keywords before opening a new report form. This carefulness can be used to reduce duplicates when the search is conducted on the fly at changes in the title text field - see bugzilla.bugzilla.org for an example. It should in general not be possible to enter reports with the same title.
This report seems to cover several things. > bugzilla.bugzilla.org Does not exist. Regarding showing potential duplicates, please attach a screenshot of what you actually refer to, and a valid full URL that actually shows the functionality (and not just the frontpage of some Bugzilla instance). > It should in general not be possible to enter reports with the same title. That's a separate thing and I strongly disagree with that. It should not be possible to do that against the very same product maybe, but I don't see any reason why bug reports with the summary "Deprecate GConf" should not be filed against those numerous projects that depend on GConf.
>> bugzilla.bugzilla.org >Does not exist. Sorry, I meant bugzilla.mozilla.org, but I just figured that the bugzillas and other issue trackers I had in mind don't do what I had in mind, i.e. they don't revalidate the search query and show similar results when the title is changed (checked bugzilla.mozilla.org, bugs.kde.org and github.com). I thought about stackoverflow.com. The popup of similar search results during typing and editing the title is what I mean. I just realized that all bug trackers should do that and admin should enable the feature given the fact their database have sufficient power, but I guess this depends on bugzilla. > It should in general not be possible to enter reports with the same title. That was imprecise again. I thought about a support for the user to avoid filing a (possibly very trivial) issue again _if it is not intended_ (the intially missing last half-sentence is the crucial part), for example I filed https://bugzilla.gnome.org/show_bug.cgi?id=742037 and https://bugzilla.gnome.org/show_bug.cgi?id=742755 and that was avoidable if I'd have been wanted after detection of an already existing report with that title. This should be obsolete when the feature discussed in the first paragraph is in place. My formulation was just nonsense. Of course, filing two reports with the same title doesn't impose any issues.
I assume that you refer to creating new tickets on enter_bug.cgi (as you wrote "before opening a new report form"), and not to changing the title of an existing bug report (as you wrote "show similar results when the title is changed"). The guided bug entry form (which is at /enter_bug.cgi?format=guided and currently not configured on GNOME Bugzilla; I might configure it at some point after GNOME Bugzilla has been upgraded to a more recent version, see bug 742340) which is not the default form provides a list of potential related bug reports or existing duplicates while you type the bug summary. A followup step (bug 742780) could be to make the guided bug entry form the default link in the header bar when clicking "New" for "default" GNOME Bugzilla users who are not (yet) member of the "editbugs" group. This is how KDE, Gentoo and Mageia have configured their Bugzilla instances, but I have not yet investigated which exact work is needed for that. It seems that these two items combined might fulfil the request in this ticket? If so, feel free to mark this as a duplicate of bug 742780.
> you wrote "show similar results when the title is changed" Yes, I mean changing the title of an yet non-existing bug during creation of a report. > see bug 742340) which is not the default form provides a list of potential related bug reports or existing duplicates while you type the bug summary. Seems to be what I want from the description, I didn't get a clear picture from the templates in the report, but I might just review that when 742340 is resolved.
bugs.sabayon.org is an example for a bugzilla instance which does what I suggested.
Looks like this is a duplicate of bug 686323 instead, which is now fixed here *** This bug has been marked as a duplicate of bug 686323 ***