Closed
Bug 1020558
Opened 10 years ago
Closed 10 years ago
Add Involved with Bugs and Never Visited Query to MyDashboard
Categories
(bugzilla.mozilla.org :: MyDashboard, defect, P2)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bholley, Assigned: dylan)
Details
(Keywords: bmo-big)
Attachments
(1 file)
1.55 KB,
patch
|
glob
:
review+
|
Details | Diff | Splinter Review |
If someone CCs me on a bug, it never shows up on the dashboard until I view it. This makes the dashboard significantly less useful as a bugmail replacement.
Comment 1•10 years ago
|
||
Bobby's suggestion was to set the last visited timestamp for the person being CCed to something in the past to make the bug appear on their dashboard which makes sense to me.
Assignee | ||
Comment 2•10 years ago
|
||
I think we could just do a custom query to search "bugs cc'd on" and "last changed great than ..." (something that is already possible with custom search and unrelated to the new last_visit feature.
Assignee | ||
Comment 3•10 years ago
|
||
Actually, there is a query called "Bugs You Are CC'd On" and you can sort that by the Updated column.
Comment 4•10 years ago
|
||
(In reply to comment #3) > Actually, there is a query called "Bugs You Are CC'd On" and you can sort that > by the Updated column. Yes, but the issue is that query is mostly uses for folks such as myself who have been CCed on thousands of bugs... Also, you could search on %last_changed% separately too, right? I would expect the set of bugs in comment 0 to be included in those results.
Comment 5•10 years ago
•
|
||
I believe the fundamental request is to treat "becoming involved with a bug"--reporting, getting assigned, becoming qa contact, or getting cced--as visiting the bug, and thus the event should be inserted into the last-visited table. This is similar to bug 1020023, except the action may be performed by someone else.
Assignee | ||
Updated•10 years ago
|
Assignee: general → dylan
Assignee | ||
Comment 6•10 years ago
|
||
As discussed in the b-team meeting, perhaps we should provide a "Involved Bugs That Have Never Been Visited" query. This would be all bugs that you have reported, been assigned, became qa contact, or got cced on. As the number of bugs that this would be true for would be very large, we could provide some mechanism (button/link) to "mark all these bugs as visited".
Assignee | ||
Updated•10 years ago
|
Summary: Bugzilla's last_changed should match bugs that I have a relationship with, even if I haven't viewed them → Add Involved with Bugs and Never Visited Query to MyDashboard
Assignee | ||
Comment 7•10 years ago
|
||
Would an "Involved With and Never Visited" query meet your needs for this feature? See comment #6. Thanks!
Flags: needinfo?(bobbyholley)
Reporter | ||
Comment 8•10 years ago
|
||
(In reply to Dylan William Hardison [:dylan] from comment #7) > Would an "Involved With and Never Visited" query meet your needs for this > feature? > > See comment #6. Thanks! I think so, yes.
Flags: needinfo?(bobbyholley)
Component: Bugzilla-General → Extensions: MyDashboard
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Updated•10 years ago
|
Assignee | ||
Comment 9•10 years ago
|
||
Adding this query will mean implementing the logic for "is involved in bug" in the SQL query. If we simply search for "every bug never visited" and then do the "is involved with" check in perl... that would be bad.
Assignee | ||
Comment 10•10 years ago
|
||
Right, totally forgot how simple the queries in MyDashboard were. I also forgot that we get an "is empty" operator. The only thing I'm not sure of is how to make the qa contact search term optional. Would it require renumbering the search terms?
Flags: needinfo?(glob)
Flags: needinfo?(dkl)
Comment 11•10 years ago
|
||
(In reply to Dylan William Hardison [:dylan] from comment #10) > The only thing I'm not sure of is how to make the qa contact search term > optional. Would it require renumbering the search terms? why does the qa-contact search term need to be optional?
Flags: needinfo?(glob)
Assignee | ||
Comment 12•10 years ago
|
||
The code below lead me to believe that it did, although it didn't make sense. extensions/MyDashboard/lib/Queries.pm: if (Bugzilla->params->{'useqacontact'}) { push(@query_defs, { name => 'qacontactbugs', heading => 'You Are QA Contact', description => 'You are the qa contact on this bug, and it is not resolved or closed.', params => { 'bug_status' => ['__open__'], 'emailqa_contact1' => 1, 'emailtype1' => 'exact', 'email1' => $user->login } }); }
Assignee | ||
Comment 13•10 years ago
|
||
Comment on attachment 8484751 [details] [diff] [review] bug-1020558-v1.patch For review
Attachment #8484751 -
Flags: review?(glob)
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(dkl)
Comment 14•10 years ago
|
||
Comment on attachment 8484751 [details] [diff] [review] bug-1020558-v1.patch Review of attachment 8484751 [details] [diff] [review]: ----------------------------------------------------------------- r=glob
Attachment #8484751 -
Flags: review?(glob) → review+
Assignee | ||
Comment 15•10 years ago
|
||
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git cf7ddf8..34cc540 master -> master
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•