29408 - bugzilla - process_bug.cgi (changing a bug) appends info on another bug

Status: VERIFIED DUPLICATE of bug 63536

(Bugzilla :: Creating/Changing Bugs, enhancement, P3)

Description

[Jesse Ruderman]

When you change a bug and hit "commit", process_bug.cgi appends information 
on "the next bug in your list". This confuses me about every other time I add a 
comment on a bug, because I think I added a comment to the wrong bug.

Suggested resolution: don't append anything. (as opposed to appending the bug 
you just modified, since the user can click "back to bug .....")

Comment 1

[Sean Richardson]

[e-mail], keep participating, eventually you'll get used to it ;-)

What is particularly annoying about this is that the next bug in the list
is often not even from the same list! This is because of bug 24896, 
"browsing two lists doesn't work". 

Since showing the next bug on the list wouldn't have been added to 
process_bug.cgi unless it was useful to someone (presumably people going
through a single bug list in order, who have no need to do other queries as 
they do so), perhaps a preference would be appropriate, so that bugzilla could 
save the effort of retreiving and sending a bug that will be ignored, and the 
user could save the effort of ignoring it, if the pref was set to "Don't show 
next bug on list". 

Comment 2

[Terry Weissman]

[e-mail] is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)

Comment 3

[Gervase Markham [:gerv]]

This bug has not been touched for more than nine months. In most cases, that 
means it has "slipped through the net". Please could the owner take a moment to 
add a comment to the bug with current status, and/or close it.

Thank you :-)

Gerv

Comment 4

[Matthew Tuck [:CodeMachine]]

I can't see any immediate proposal that will please everyone, maybe a user pref.

Comment 5

[Stephan Niemz]

moving to real milestones...

Comment 6

[Dave Miller [:justdave]]

no reason this needs to be "futured".  There's people on my site who have 
complained about the same thing (in fact, it's hacked to show the same bug again 
on my site).  Let's get a user preference in for it or something.

After posting changes to a bug:
 (*) Show me the same bug again
 ( ) Show me the next bug in my last bug list
 ( ) Only show me the confirmation of changes.

Should default to same bug for new users, the conversion scripts in checksetup.pl 
should set it to next bug on any existing users that are converted.

Comment 7

[Matthew Tuck [:CodeMachine]]

Moving to new Bugzilla product ...

Comment 8

[John Levon]

This UI sounds like a great idea. I would /love/ it to show the same
bug again. I've just entered loads of bugs (moving bugs from another
tracker product) and it is awkward as hell having to go back, behind
a 56k modem with bug 25521 still open !

Surely this one isn't too hard to do ;)

Comment 9

[Jesse Ruderman]

I don't see any point in showing the same bug again.  Most of the time, you're
not going to look at the bug you just changed, so showing it will only slow down
bugzilla and your browser.  If you need to, you can just press your browser's
back button.

I think John is talking about what you see after entering a new bug.  I agree
that it would make sense to show the bug in that case.

Comment 10

[Dave Miller [:justdave]]

Not everyone works like that.  I for one almost always click the "Back to bug
XXXX" link after updating a bug, just to make sure that what I thought I did to
it is really what happened, or sometimes to re-read my comment again to make
sure I didn't screw something up in it.  Hitting the Back button is a bad idea
in this case because then you get the cached copy before your changes (although
with the controls you modified still modified).  I'd like to be able to switch
between modes on the fly if possible.  when I'm modifying individual bugs, I
usually like to go back to that bug after making changes.  If I'm triaging a
buglist, going to the next bug is really handy.

Comment 11

[John Levon]

I'm not just talking about new bugs. I've lost count of the number
of times I've clicked that link. And we are talking about making
this configurable.

If every single bug was fixed in bugzilla so I could make /all/ changes
at once, then I would have no need for it. As it is, it's of a great
advantage to me.

I assume that "all at once" is of interest to the bugzilla developers
if only because it reduces bugspam - I'd like to see this even more :)

Comment 12

[Andreas Franke (gone)]

Bug 63536 is the same thing, isn't it? Not sure which one to dupe, though...

Comment 13

[Jesse Ruderman]

*** This bug has been marked as a duplicate of 63536 ***

Comment 14

[Dave Miller [:justdave]]

clearing target milestone on invalid/duplicate/worksforme/wontfix bugs so
they'll show up as untriaged if they get reopened.

Comment 15

[Matt Perry]

Verified dupe