Platform/Layout/Backlog: Difference between revisions
(Add descriptions of how backlog is managed, add "unowned" bug section) |
(→How We Track Our Backlog: updated to include newer flags and not the whiteboard backlog tag) |
||
Line 1: | Line 1: | ||
= How We Track Our Backlog = | = How We Track Our Backlog = | ||
All tracking of backlog and work-in-progress items happens in [https://bugzilla.mozilla.org/ Bugzilla]. | All tracking of backlog and work-in-progress items happens in [https://bugzilla.mozilla.org/ Bugzilla]. | ||
There are several flag used to track work in Bugzilla including: | |||
* [https://wiki.mozilla.org/BMO/UserGuide#Tracking_Flags Tracking Flags] | |||
* [https://wiki.mozilla.org/BMO/UserGuide#Status_Flags Status Flags] | |||
* [https://wiki.mozilla.org/BMO/UserGuide#Project_Flags Project Flags] | |||
* [https://wiki.mozilla.org/BMO/UserGuide#Needinfo_Flag Need Info Flags] | |||
We use bug priorities to indicate how soon we plan to work on a bug, task or enhancement according to the following classifications (also documented in our [https://firefox-source-docs.mozilla.org/bug-mgmt/guides/priority.html Firefox-wide priority definitions]): | We use bug priorities to indicate how soon we plan to work on a bug, task or enhancement according to the following classifications (also documented in our [https://firefox-source-docs.mozilla.org/bug-mgmt/guides/priority.html Firefox-wide priority definitions]): |
Revision as of 18:00, 5 March 2024
How We Track Our Backlog
All tracking of backlog and work-in-progress items happens in Bugzilla. There are several flag used to track work in Bugzilla including:
We use bug priorities to indicate how soon we plan to work on a bug, task or enhancement according to the following classifications (also documented in our Firefox-wide priority definitions):
- P1 — "Must have/fix." Under active development, or planned development during the current release cycle.
- P2 — "Should have/fix." Near-term backlog item, can/will be worked on starting in the next release cycle or the one after that.
- P3 — "Would like to have/fix." Longer-term backlog item, planned to work on within the next year (assuming the bug also has the
[layout:backlog]
whiteboard tag). - P4 — N/A
- P5 — "Will not fix." No plans to work on this item, but will accept contributor patches.
Definition of Assigned
A bug is considered "assigned" if it has both an assignee AND its status is set to ASSIGNED
. Having only one of these fields set is not sufficient for it to be tracked as an assigned bug.
Commonly-Used Backlog Queries
Kanban View
For quick reference, view our backlog as a kanban board.
Backlog by Category
In Progress
Bugs, tasks, and enhancements that are in progress right now. This list includes any bug, task or enhancement that is assigned and has the [layout:backlog]
whiteboard tag.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Needs Owner
Bugs, tasks, and enhancements that should be in progress, but currently do not have an assignee. This list includes unassigned P1 tasks, enhancements, and bugs with the [layout:backlog]
whiteboard tag.
ID | Summary | Assigned to | Status | Resolution |
---|---|---|---|---|
939897 | [meta] Support shifting / splitting flex items between continuations of a fragmented flex container (flexbox content truncated when printing) | NEW |
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Upcoming
Bugs, tasks, and enhancements we are considering working on within the next 2-3 releases. This list includes unassigned P2 tasks, enhancements, and bugs with the [layout:backlog]
whiteboard tag.
5 Total; 5 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Backlog
Bugs and enhancements we are considering working on within the year. This list includes all unassigned P3 tasks, enhancements, and bugs with the [layout:backlog]
whiteboard tag.
21 Total; 21 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Recently Fixed in Nightly
Bugs, tasks, and enhancements that have landed in the current nightly.
ID | Summary | Assigned to | Status | Resolution |
---|---|---|---|---|
1639816 | Printing local pages via Print Menu fails with In Printing:Print:Done handler, got unexpected rv 2147746065 | Jonathan Watt [:jwatt] | VERIFIED | FIXED |
1 Total; 0 Open (0%); 0 Resolved (0%); 1 Verified (100%);
Recently Fixed in Beta
Bugs, tasks, and enhancements that have landed in the current beta.
ID | Summary | Assigned to | Status | Resolution |
---|---|---|---|---|
1584890 | abspos root element (html) ignores top/right/bottom/left properties, if it has "display:flex" or "display:grid" | Ting-Yu Lin [:TYLin] (PDT, UTC-7) | RESOLVED | FIXED |
1622935 | Support pushing and splitting flex items for single-line (and some multi-line) flex container | Ting-Yu Lin [:TYLin] (PDT, UTC-7) | RESOLVED | FIXED |
1626129 | Height computation for (nested?) box is somewhat different in printing | Ting-Yu Lin [:TYLin] (PDT, UTC-7) | RESOLVED | FIXED |
1564128 | Unable to print CSS animations/transitions and web animations | Emily McDonough [:alaskanemily] | RESOLVED | FIXED |
4 Total; 0 Open (0%); 4 Resolved (100%); 0 Verified (0%);