4 ms·
Estimation is a killer feature missing from Github Issues, and it looks like you've got a points estimation feature, which is great. Any plans to add hour-base
by alexwebb2 11y ago
Estimation is a killer feature missing from Github Issues, and it looks like you've got a points estimation feature, which is great.
Any plans to add hour-based estimation?
- jenniferDewalt 11y agoThat's a great idea and would be pretty quick to add. Would having either points or hours for a repository work for you?
- lisivka 11y agoIf in hours, then implement it as combobox with predefined list of standard estimates (1h, 2h, 4h, 1d, 2d, 3d, 1w, 2w, 3w, 1m, 2m, 3m, 6m, 1y).
- jenniferDewalt 11y agoGot it! That makes sense, thanks for the breakdown.
- alexwebb2 11y agoYeah, that'd be fantastic!
- kwiens 11y agoIt's critical to have point estimates available in Github. Zenhub, Codetree, Waffle, and others are moving to sync issue point estimation with integer labels in Github. We heavily use `1`, `2`, etc. labels in Github and have built a lot of tooling on top of their API. We'd love to use Zube, but you either need to use Github as the data source for point estimates or build a comprehensive API.
- jenniferDewalt 11y agoInteresting. Maybe we could make an app setting that would save points as labels. Thanks for suggesting it! And we will release a public API :) You can already see much of the functionality in Zube's Issue Manager.