Facilitate entering multiple bugs in the same product

NEW
Unassigned

Status

()

Bugzilla
Creating/Changing Bugs
--
enhancement
13 years ago
8 years ago

People

(Reporter: tyler, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 2.18

When I commit a new bug I am dumped back onto the generic product list page and 
have to select the product again before I can enter the next bug.  It would be 
much more efficient if the system retained the product variable and allowed me 
to add a sequence of new bugs to that product.

Reproducible: Always

Steps to Reproduce:
1.start @ enter_bug.cgi and select the 'KILLERAPP' product from the list.
2.fill in enter_bug.cgi?product=KILLERAPP page and commit.
3.watch your window refresh to enter_bug.cgi and make you select the product 
again before you can enter another bug.



Expected Results:  
Allowed me to enter another bug within the same product.

Updated

13 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: Commit new bug - retain current product variable → After adding bug, offer link to enter bug in the same product

Comment 1

13 years ago
This translates mostly into:

"After adding bug, offer link to enter bug in the same product"

Alternatively, we can have a cookie or a server-stored value regarding the
product where the last bug was filled in by that user (or retrieve it doing SQL
query in enter_bug.cgi), and preselect that product by default if no default
value is given in the URL.
Summary: After adding bug, offer link to enter bug in the same product → Facilitate entering multiple bugs in the same product
I think a nicer alternative might be to replace the "New" link in the footer
with a dropdown containing all the products.  That way, when you want to add a
new issue (at any time), you just select something from the dropdown list and
you're off to the races.

I can provide a patch if there's a need, but I know the footer is being
redesigned, so let's see where this one lands.

Comment 3

13 years ago
Isn't that what the "Remember values as bookmarkable template" button is for? 
(Would be nice if the bookmark didn't default to being called "this link" 
though, but that's another bug ;-) )

Also, depending on browser, a user may be able to use the back button, modify 
the summary / description and hit "Commit" again.


If a link is provided to allow a similar bug to be entered, there would 
presumably be some argument over how much of the "original" bug should be 
preserved... e.g. Usually Platform/OS would be the same, and Component might 
often be the same too. Sometimes you might want to enter a series of bugs all 
blocking a common tracking bug. Sometimes a series of related bugs would even 
have little difference in summary / description.

Personally I don't see a compelling reason to have this when bookmarkable 
templates already exist, and allow the user to bookmark exactly the level of 
detail that is in common between [most of] the bugs to be entered.

Comment 4

13 years ago
*** Bug 310030 has been marked as a duplicate of this bug. ***

Comment 5

13 years ago
(In reply to comment #3)
[...]

On re-reading this bug, I see that I was going off on a different tangent to the
main thrust of this bug. Yes it would be nice after submitting a bug to have a
"Report another bug in the $product product" link, for the main reason it saves
one or two extra page loads.
[mark comment #3 as obsolete]

Comment 6

11 years ago
I'm planning to fix it like comment 1 suggests.. meaning just like after adding an attachment you get an 'add another attachment for this bug', I plan to add a 'file another bug in product $FOO'.
Assignee: create-and-change → bugzilla-mozilla
Target Milestone: --- → Bugzilla 3.2

Comment 7

10 years ago
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.
Target Milestone: Bugzilla 3.2 → ---

Updated

8 years ago
Assignee: bugzilla-mozilla → create-and-change
You need to log in before you can comment on or make changes to this bug.