Skip to content

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

Merged
merged 45 commits into from
Mar 18, 2024

Conversation

dklawren
Copy link
Collaborator

@dklawren dklawren commented Jan 7, 2024

  • 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

- 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
@dklawren dklawren added the WIP label Jan 7, 2024
- 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
@dklawren dklawren removed the WIP label Jan 25, 2024
@dklawren dklawren requested a review from cgsheeh January 25, 2024 22:07
…ntion report was not working. So went a different route.
@dklawren dklawren requested a review from cgsheeh March 12, 2024 17:11
dklawren and others added 18 commits March 12, 2024 13:30
…d so we should try to grab the next one up to 5 tries
…only update the class and not actually copy the data
…to Google Artifact Registry instead od Github Container Registry
dklawren and others added 18 commits March 12, 2024 13:30
… is released, disabled old versions and milestones 10 releases or older
…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
Comment on lines 84 to 87
[% IF debug_output %]
<pre>[% debug_output FILTER html %]</pre>
[% END %]

Copy link
Collaborator

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?

Copy link
Collaborator Author

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.

@dklawren dklawren merged commit 5677283 into mozilla-bteam:master Mar 18, 2024
@dklawren dklawren deleted the 1859442 branch March 18, 2024 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants