-
Notifications
You must be signed in to change notification settings - Fork 189
Bug 1859442 - What Should I Work On Next: rename and enhancements #2162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Rename to "What Needs My Attention?" - Internal rename from `whats_next` to `attention` - The URL should be `bugzilla.mozilla.org/attention` - Redirect from the current URL
- Add a link to the documentation: https://firefox-source-docs.mozilla.org/bug-mgmt/policies/attention-dashboard.html - Add the following to the top of the page, below the auto-refresh toggle: - `Code review requests are not visible on this dashboard; please visit Phabricator to view those. In general it’s reasonable and important to prioritize Review Requests to unblock others.` - The word `Phabricator` should link to https://phabricator.services.mozilla.com/ - `Highest Priority Tasks` section: - Change the subtitle to: - `These are the things you should drop everything else for. Generally, work where you block others should be addressed as higher priority than non-blocking work.` - Rename `Important NEEDINFOs` to `Critical NEEDINFOs` - Rename `sec-critical bugs` to `Security-Critical Bugs` - Change the order of the tables to: - Critical NEEDINFOs - S1 Bugs - Security-Critical Bugs - `High Priority Tasks` section: - Change the subtitle to: - `High priority tasks are also "drop everything", except that in this case "everything" doesn't include anything in the "Highest priority" list. Generally, work where you block others should be addressed as higher priority than non-blocking work.` - Rename `Other NEEDINFOs` to `Important NEEDINFOs` - Rename `sec-high Bugs` to `Security-High Bugs` - Remove the `Regressions` list - Change the order of the tables to: - Important NEEDINFOs - S2 Bugs - Security-High Bugs - Other NEEDINFOs
…ntion report was not working. So went a different route.
- Updated test case to match
…d so we should try to grab the next one up to 5 tries
…o the end of fields
… selected person's email into the text box
… single drag gesture
…ect> element having no search bar
…only update the class and not actually copy the data
…to Google Artifact Registry instead od Github Container Registry
… <bz-sel…" This reverts commit 676e5bf.
…wns in a…" This reverts commit 520653a.
This reverts commit de24d32.
… to go t…" This reverts commit f5bcfb3.
…h search…" This reverts commit a8a2ae3.
… is released, disabled old versions and milestones 10 releases or older
…ills the…" This reverts commit e9625d9.
…duo 2fa for certain members
…d data to google cloud storage instead of aws s3
…tgoing links to work properly with Google Cloud Storage
…meters and create special group that can administer it
[% IF debug_output %] | ||
<pre>[% debug_output FILTER html %]</pre> | ||
[% END %] | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intentionally left in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not intentional really. I had the debugging there which proved useful when the queries were not giving the expected results. But now that they are working properly, I can remove the debugging code. Will do that before merge.
whats_next
toattention
bugzilla.mozilla.org/attention