Open
Bug 398163
Opened 18 years ago
Updated 11 years ago
Implement UI (and backend code if required) to easily query the activity of bugs
Categories
(Bugzilla :: Query/Bug List, enhancement)
Tracking
()
NEW
People
(Reporter: LpSolit, Unassigned)
Details
(Whiteboard: [wanted-bmo])
Earlier today, I wanted to watch all changes made by a specific user (whom I suspected to be a spammer). But there is no way to do it. I would like a simple UI to:
- restrict changes made by a specific list of users
- restrict products/components to look into
- restrict the time range to look into
The last 2 requests are already available in query.cgi; only the first one is missing. Also, the UI should be a table with all changes from specified users only (if given), i.e. it should have a look similar to show_activity.cgi. Maybe a toogle button which lets you go from a buglist to a table à la show_activity would be useful too.
Updated•18 years ago
|
Whiteboard: [wanted-bmo]
![]() |
||
Comment 1•18 years ago
|
||
This should just be done as an enhancement of the code for show_activity.cgi.
We can make it take multiple bug_ids, and then it will show all the changes in time order.
We can make it take a user, and it will show all changes made by that user.
And we can make it take a time range.
Even better, we could enhance Search.pm to take real parameters instead of a CGI object, and give show_activity the ability to take the same parameters as buglist.cgi.
![]() |
Reporter | |
Updated•18 years ago
|
Assignee: query-and-buglist → LpSolit
Target Milestone: --- → Bugzilla 3.2
![]() |
Reporter | |
Updated•18 years ago
|
Target Milestone: Bugzilla 3.2 → Bugzilla 4.0
![]() |
||
Comment 2•18 years ago
|
||
It would be nice to simply add a changedby field to the "Bug Changes" section of the advanced search page, since so much similar functionality is provided there.
![]() |
||
Comment 3•18 years ago
|
||
Bug 214851 would also provide this behavior.
![]() |
Reporter | |
Updated•15 years ago
|
Assignee: LpSolit → query-and-buglist
![]() |
Reporter | |
Comment 4•13 years ago
|
||
We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.
I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else on time for 5.0.
Target Milestone: Bugzilla 4.4 → Bugzilla 5.0
![]() |
||
Updated•11 years ago
|
Target Milestone: Bugzilla 5.0 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•