Board list capacity
- This is after we have #3772 (closed)
- Every board list can have two associated capacity values.
- There is some UI to set this per list, probably at the top.
- Update the board UI so that the lists either show only issue counts or summed weights. Probably configured in the edit board modal. This is to make sure there’s not too many numbers clogging up the top of the board list.
- So each list has a capacity value associated with issue counts and a capacity value associated with summed weights.
- So per list, you show the user-configured capacity value and the actual count/summed weights of the issues in that list. So visually you can see if you are above or below capacity. If you are above, you may want to have some warning, like a red color.
- This applies to all three list types: Labels, assignees, and milestones.
Milestone list use cases
- This is available after #6469 (closed).
- If you are planning future milestones’ work in a board, you enter these list capacities. So then as you put issues into those milestones, you know if you are over scheduling.
- You can drag issues between milestones to balance out.
- You can adjust a milestone’s capacity if you know that in that period, someone will be on vacation.
- For current or past milestones, you can see work remaining in terms of count/weight compared to original capacity. Sort of like burndown.
- Since the board is already scoped, everything is with respect to that scope, for example, a team.
Assignee list use cases
- This is similar to milestone lists. But it’s scoped to a person. So if you want to plan capacity per individual, this allows you to do that.
- So you could have a board that represents team assignments for the 11.3 milestone. Right away you can see if you are over or under scheduling per person.
Label list use cases
- If you are using label lists to plan a single milestone, you can set capacity limits per area. This can be a way to balance out say tech debt vs UX polish vs new feature development.
- If you are using label lists to track workflow (eg within a single milestone) then you can set limits per stage. This is a way to avoid/manage bottlenecks of issues building up in s certain stage. Some Agile-like methodologies explicitly do not allow you to have too many accumulation in a given stage at a given time.