Closed
Bug 1069363
Opened 10 years ago
Closed 10 years ago
"show user list again" link does not include is_enabled for showing previous results list
Categories
(Bugzilla :: Administration, task)
Tracking
()
RESOLVED
FIXED
Bugzilla 4.4
People
(Reporter: dkl, Assigned: dkl)
Details
Attachments
(2 files)
625 bytes,
patch
|
glob
:
review+
|
Details | Diff | Splinter Review |
627 bytes,
patch
|
glob
:
review+
|
Details | Diff | Splinter Review |
When searching for users and then returning to the seearch form in editusers.cgi, the previous value of "Restrict search to 'All|Enabled|Disabled' users" is not passed through properly.
Found this by running test_user_groups.t selenium test.
dkl
Assignee | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
Bugzilla 4.4 also has this problem, so I'm a bit surprised that you only see the Selenium script fails on trunk, unless you changed the code.
Severity: blocker → normal
OS: Linux → All
Version: unspecified → 4.4
Comment on attachment 8491528 [details] [diff] [review]
1069363_1.patch
Review of attachment 8491528 [details] [diff] [review]:
-----------------------------------------------------------------
r=glob
Attachment #8491528 -
Flags: review?(glob) → review+
4.4 needs a different patch, because the field name is "enabled_only" there.
Target Milestone: --- → Bugzilla 4.4
Assignee | ||
Comment 5•10 years ago
|
||
Attachment #8492377 -
Flags: review?(glob)
Assignee | ||
Updated•10 years ago
|
Flags: approval?
Comment on attachment 8492377 [details] [diff] [review]
1069363_4_4_1.patch
Review of attachment 8492377 [details] [diff] [review]:
-----------------------------------------------------------------
r=glob
Attachment #8492377 -
Flags: review?(glob) → review+
Assignee | ||
Comment 7•10 years ago
|
||
To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git
5d96fa7..6b518aa master -> master
To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git
e9f5fda..392fcaf 4.4 -> 4.4
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Flags: blocking4.4.6?
Resolution: --- → FIXED
this issue isn't important enough to warrant the blocking flag.
the litmus test is if we should cut a release immediately to deploy this fix; that isn't the case with this issue as it's a relatively minor bug.
Flags: blocking4.4.6? → blocking4.4.6-
You need to log in
before you can comment on or make changes to this bug.
Description
•