[FR] Break down Remaining Work/Finished work columns (i.e. on IterationView) by priority (P1, P2, P3)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by locating the IterationView and the existing Remaining Work and Finished work calculations. Review how iteration data is presented, then clarify whether the priority breakdown belongs in IterationView or a new Capacity view; the work is done when the agreed priority analysis is displayed and validated against iteration totals.
Written by the indexing model from the issue text.
Description
After discussion with Richard and Lee, we think the Remaining Work column would be more useful if you could identify the total count of P1 points vs. P2 points and so on. This would help us track how many points worth of bugs we're delivering vs. are in flight, so we can better estimate prioritization. Ideally, we want the number of points finished per iteration to be roughly the same as the number of P1 points in flight on average during the iteration.
We may not want to put these extra details in the bottom of the IterationView. Instead, we could put this analysis in a separate "Capacity" view. In the long term we can add useful info to this view. For example, Richard suggested a graph mapping finished points per iteration could be useful. That's a separate thing but you can see how it'd be useful to have snapshots of how much work we finished for each iteration vs. how much we committed to.
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mozilla/bugzy
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
[FR] Add qe-verify flag tag on recently closed bugs under "My Bugs'May be free again @mimizillaa claimed this 872 days ago, and no pull request is open. Openenhancement
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
solana-foundation/solana-com#2245 ·
Maintainers usually reply within 1 day
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TAMULib/fw-registry#543 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
`document.cookie` with `max-age=0` does not delete the cookiePossibly taken @BartInTheField claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
capricorn86/happy-dom#2460 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Seeed-Studio/wiki-documents#5720 · 1 comment ·
Maintainers usually reply within 1 day