Benefit-cost score

• Teams want a way to characterize high return work, as a signal to indicate what to work on.
• For example, if a feature requires very little effort, but has a huge business impact, then teams should prioritize this higher.
• Since GitLab has a lot of these metrics already, it would be ideal to allow a score to be calculated, possibly per issue or per epic.
• The "cost" part could be characterized by the issue weight, or summed weights in an epic.
• The benefit could be gathered through priotized labels, or other new fields.
• And then the benefit-cost score could be a weighted ratio.