Closed
Bug 100390
Opened 23 years ago
Closed 23 years ago
after commit of a new comment, don't follow "next" link
Categories
(Bugzilla :: Creating/Changing Bugs, defect, P3)
Tracking
()
People
(Reporter: smcpeak, Assigned: myk)
Details
After I add a comment to an existing bug and press commit, the page that
loads next has a blurb at the top confirming what I did, but the rest of the
page is whichever bug happens to be "next" -- not at all what I expect or want!
I invariably click on the "back to bug <whatever>" link to make sure my
comments are properly formatted, make sense in context, etc.
I think committing a comment should keep you on the same bug page.
I think that this should be a user-option: after committing changes to a bug,
either show the next bug (which I'm sure is a facility that some people use), or
show the bug you just changed, which some people expect, or would prefer.
(There could also be other options, e.g. go back to the buglist.)
The user prefs are on bug#98123
Depends on: 98123
Comment 2•23 years ago
|
||
I'd like this too, I operate on bug lists in multiple windows, so I don't use
the 'next' feature of buglists, but automatically reshowing the bug would be
real nice.
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18
Comment 3•23 years ago
|
||
Ditto most comments, but an additional comment, which I think is really a bug,
not an RFE: Upon committing a change, I am indeed taken to the next bug, which
isn't so bad, but if I want to look at the bug I just changed, clicking
"Previous" should do that, only it doesn't -- it takes me to the one BEFORE the
one I changed. Only clicking "Next" from here brings me to the bug I modified.
Too many clicks. Bad interface.
The select "Take me back to bug #XXX" (the one I just changed) isn't quite good
enough IMHO.
Comment 4•23 years ago
|
||
*** This bug has been marked as a duplicate of 63536 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Target Milestone: Bugzilla 2.18 → ---
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•