Bug 80270 - RFE: Add preference for next to be displayed when making changes
Summary: RFE: Add preference for next to be displayed when making changes
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General   
(Show other bugs)
Version: 2.18
Hardware: All
OS: Linux
medium
medium vote
Target Milestone: ---
Assignee: David Lawrence
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-12-23 18:16 UTC by David Lawrence
Modified: 2007-04-18 16:49 UTC (History)
3 users (show)

Fixed In Version: 2.18
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-04-20 17:52:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description David Lawrence 2002-12-23 18:16:05 UTC
Description of problem:
When a change is commited the default Bugzilla behaviour is to skip to the next
bug in a members query list. There needs to be a preference to disable/enable
this behaviour depending on how the developer wants it to happen. I would like
to stay away from adding more COOKIES than necessary so this will require a db
schema adjustment.

Version-Release number of selected component (if applicable):
2.17.1

Comment 1 David Lawrence 2006-04-08 18:02:01 UTC
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.

Comment 2 Aleksey Nogin 2006-04-08 18:49:24 UTC
Still there.

Comment 3 Mike A. Harris 2006-04-20 17:39:38 UTC
Thankfully our bugzilla default is to disable that annoying behaviour though,
so there probably isn't a lot of incentive to add this feature. ;o)


Comment 4 David Lawrence 2006-04-20 17:52:14 UTC
As long as mharris is happy with our current default then I consider this a
non-issue ;)


Note You need to log in before you can comment on or make changes to this bug.