Inline dupe-finding: an exercise in pain reduction
For the last million years1 or so I’ve been working on a cool new feature for Launchpad Bugs: an inline, AJAXified, asynchronous dupe finder.
For quite some time now people have encountered timeouts or long response times when trying to file bugs, particularly when they enter a long bug summary or the project that they’re filing the bugs on has a lot of bugs through which Launchpad has to search in order to be able to find possible duplicates. The upshot was that whenever a timeout occurred people were unable to file a bug and would have to back up and start again. Needless to say, this was frustrating for all involved.
The new inline dupefinder, which you’ll now find on the “Report a bug” page of any project in Launchpad (when viewed on edge.launchpad.net) is designed to stop this from being a problem, or at least to reduce the problem to a more manageable level and stop it from getting in peoples’ way. It does this in two ways:
- The inline list of duplicates is much quicker to render than a full Launchpad page.
- If the search for duplicates times out for some reason you’ll still be able to file a bug.
Here’s the catch: we need your help. Launchpad’s development cycle this month is very short due to the approaching year-end holiday period, so we need to get as much testing done on this as possible. Check out the dupe finder, see if it works for you and, most importantly, report a bug if it doesn’t.
One last thing: at the time of writing, the inline dupe finder only works for projects (like Launchpad Bugs), not for packages or project groups. We’ll hopefully be enabling it for project groups today and with a bit of luck for packages, too. We started off with projects only because it’s the simplest implementation of the concept and it gives us a good base to test from.
Thanks in advance for your help. Let’s make Launchpad awesome together!
1 This might be an exaggeration.
December 10th, 2009 at 1:36 pm
Sorta works. If it finds no relevant bugs, the button to report a new bug does not show.
December 16th, 2009 at 10:31 pm
[…] nice change is the filebug work that Graham already posted about when he put out his call for early testing. This changes lands with 3.1.12 and filing a bug should rarely time out […]