Closed
Bug 1225902
Opened 8 years ago
Closed 4 years ago
Show only flags with requestee in the "Flags You Have Requested" section
Categories
(bugzilla.mozilla.org :: MyDashboard, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: RyanVM, Assigned: kohei.yoshino)
Details
Attachments
(2 files)
I've set in-testsuite? a *lot* over the last 7+ years. To date, I have over 700 such requests. This makes the "Flags You Have Requested" section of my dashboard difficult to use effectively, and I really don't have much ownership over those requests besides happening to the be person who set them. It would be great if I could filter those out so I could get a much better view of the requests I actually care about following up on.
Assignee | ||
Updated•4 years ago
|
Type: defect → enhancement
Comment 1•4 years ago
|
||
Could you please ignore in-testsuite? in the dashboard?
It isn't that interesting compared to review or needinfo
thanks
Flags: needinfo?(kohei.yoshino)
Assignee | ||
Comment 2•4 years ago
|
||
Can do.
Assignee: nobody → kohei.yoshino
Status: NEW → ASSIGNED
Flags: needinfo?(kohei.yoshino)
Assignee | ||
Comment 3•4 years ago
|
||
This is RyanVM’s request queue: https://bugzilla.mozilla.org/request.cgi?action=queue&requester=ryanvm%40gmail.com&group=type 😱
Basically we should only show flags with the requestee (it’s called “specifically requestable” flags) so in-testsuite?
, qe-verify?
, etc. will be filtered out.
Summary: Allow users to filter out certain flags from the "Flags You Have Requested" section → Show only flags with requestee in the "Flags You Have Requested" section
Assignee | ||
Comment 4•4 years ago
|
||
Note that this only makes a change to My Dashboard. The Request Queue (My Requests) page will remain as is, and it’s probably okay.
Assignee | ||
Comment 5•4 years ago
|
||
Merged to master.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•4 years ago
|
||
Assignee | ||
Comment 7•4 years ago
|
||
The follow-up PR also merged to master.
You need to log in
before you can comment on or make changes to this bug.
Description
•