Enter something to (quick) search for:
Enter an e-mail address to observe bugs that said person commented
on that have had recent activity:
Bugzilla quick search payload
- qs=gloda is like typing "gloda" in the bugzilla quick
Search on an e-mail e-mail address, looking for bugs that
match that e-mail and were modified in some recent time
interval. Supports an optional 'why' attribute to specify
what we should use the e-mail address to search for. If
omitted, we assume "commenter". Supports an optional
'howrecent' attribute to specify the amount of time into the
past we should check which defaults to 7 days ago (7d).
Indicate what we want to search on the e-mail for. This
can be used multiple times to specify one or more of the
following values. If omitted, we assume "commenter".
If you only want to search on one thing, you can instead
just use assignee, reporter, cc, or commenter as keys
(where the value is the e-mail address.)
How recently should the message have changed. If omitted, we
assume one week. The syntax for this uses bugzilla's
query syntax, which is not amazingly intuitive. Syntax
regexp-wise is: (-|\+)?(\d+)([hHdDwWmMyY]). Where the
- Hours Ago. If the amount is zero, it
means at the top of this hour.
- Days ago, at the start of that day. (So
not this time, 2 days ago, but the very start of 2 days ago.)
- Weeks ago, at the start of that week.
Where sunday is the start of the week.
- Months ago, at the start of that month.
- Years ago, at the start of that year.
You should never use a negative sign, as your search
will match nothing and make very little sense.
- firstname.lastname@example.org queries for bugs changed in the past week
where they commented.
queries for bugs changed in the past week where they are
the assignee or reporter.
- email@example.com searches for bugs changed in the past
week where they are on the cc list.
- firstname.lastname@example.org&howlong=3d Bugs reported by
email@example.com that have changed in the last 3 days.
Set the initial sort to use. This should be one of the
attribute names with a "." prepended (this is exhibit syntax).
These are exactly what you see if you click on the "sorted by"
option (except for the period). If you want to use multiple
sort orders, comma-delimit and make sure every attribute
starts with a period. You should also consider setting
- sortBy=.num to sort by bug number
- sortBy=.assigned_to_realname to sort by the name of the
- sortBy=.changeddate,.num to sort by the changed date and
then the bug number. Be sure to do
sortOrder=descending,ascending or whatever you desire there too.
Set the initial sort order. The value should be either
"descending" or "ascending". If you are setting multiple sort
columns using sortBy, you should include a comma-delimited
list of the values.
- sortOrder=descending,ascending for when sortBy has two
Specify whether the display should be "grouped as sorted" initially.