Codetree changelog
Codetree changelog






Codetree now provides Epics for your GitHub issues. Epics are a building block to help you get better insight into the state of your software project. With Codetree Epics, you can:

  1. Group a large feature's component issues together
  2. Easily understand the state of a large feature's component issues

Here's how Epics help you understand the state of your software project.

1. Group a large feature's component issues together

We look at an Epic as a temporary (it gets closed) container that represents a feature that can be broken into smaller issues. The epic groups together the set of "component" or "child" issues that make up the feature. When the child issues are completed, the larger feature is ready to deliver to customers.

In GitHub you can group issues together with labels or milestones (if your milestones aren't date-based), but it's painful.

A Codetree Epic is simply a GitHub issue with some special sauce: you can add it to a milestone, and add assignees and labels to it. The Codetree special sauce means an Epic acts as a container for any child issues you add to it.

Here's how to add an issue to an Epic:

Once you've added issues to your epic, you want to understand what's left before the feature is done. Which brings us to the second scenario we built Epics to solve...

2. Easily understand the state of a feature's component issues

Once you have an Epic, you can get insight into the status of its issues.

For example, you can see at a glance the progress on that Epic in terms of issues closed or points completed:

You can see what stage the Epic's issues are in:

You can visualize an Epic's issues in stages on the board:

And you can re-milestone or re-assign them in list view:

We've been dog-fooding Epics internally for over a month. We've found it useful to understand what's going on with the Codetree project we use to build Codetree. We hope you find it useful too, and remember: we're always keen to hear how we can make it better for you.