Estimating Issues in Codetree

To estimate issues in Codetree, you need to first turn estimates on for the project. This doc walks you through how to do that, and how to estimate issues in Codetree after you turn them on.

First, turn estimation on for your project.

We don't have a unit attached to estimates so we call them "points". You can use them to represent hours, days, complexity, or whatever you like.

You can estimate an issue from the modal (bonus - use the "s" keyboard shortcut to pop open the size field when the modal is open):

You can estimate issues in the table view like this (you can hit tab to move to the next issue's estimate field)

You can estimate on a Kanban board like this (if you want to move to the next issue's estimate field, tab works here too):

You can see the sum of the estimates for all the issues in the table view here:

On a Kanban board you can see the sum of the estimates for all issues in a stage here:

When you add an estimate to an issues, we add a label to the issue called "size: N" where N is the estimate you gave the issue. We only show that label in Codetree in the Issue's activity stream, but that label is synced back to GitHub so you can see an issue's estimate in GitHub:

And the "size" label will appear in GitHub: