Release_scope
Estimated hours per person, summed across the whole tree, so you can ask the one question a release plan usually skips: can the people actually on this release fit the work into the weeks before code freeze?
Read it at planning time, not at the end. If one person is carrying twice anyone else, the release is already late and the roadmap has not admitted it yet.
Group by member is the default. Switch Group by to a field like Release, or add a column such as Customer requests, to slice the same data differently.
| assignee | status | name | priority | start | due | Customer requests | duration | totalTimelogs | billingTimelogs | totalBillingTimelogs | totalEstimated | completedAt | timelogs | estimated |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Darrell Finley | 4 | 1 | 2027-09-23 | 65 | 304200 | |||||||||
| Elian Glace | 4 | 1 | 2027-09-23 | 34 | 349200 | |||||||||
| Felipe | 12 | 1 | 2027-08-12 | 25 | 79200 | |||||||||
| Pak Youngjae | 3 | 2 | 2027-09-08 | 59400 | ||||||||||
| Sammy Walter | 4 | 0 | 2027-09-09 | 9 | 144000 | |||||||||
| 0 | 1 | 2027-10-01 | 42 |
Project: Product Roadmap