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.

Perfy Mcperferson

Two things to make Codetree much faster:

  1. We've migrated to a much faster database than the old Heroku Hamsterwheel that Codetree used to live on.
  2. We've optimized a bunch of queries to make them a lot faster.

In two GIFs...

Here's the old Codetree database:

Here's the new Codetree database:

Recently accessed issues list

What was that issue I just edited? Oops... forgot the milestone! There is now a handy little list of your five most recently accessed issues in the sidebar below your custom filters.

Fixed duplicate labels

Fixed an issue where in certain circumstances an issue could end up with duplicate labels.

Fix a bug in PR display

Yikes... closed PRs were showing as merged instead of closed. Now they show as closed.

Fixed a bug in board view filtering

Board view filters that included a specific milestone and 'no milestone' weren't working correctly. Now they are.

Seeing an assignee's avatar multiple times? No longer.

Fixed a race condition that was causing an assignee's avatar to show up on an issue multiple times.

Only check Assignees that are Assigned to an issue

In the inline assignee menu on List View we would sometimes have checked assignees that had been unassigned from the issue.

No longer!

Improved issue timeline

Issue timelines now include links to commits that reference an issue in their commit message and references made to other issues in issue comments.

Quickly get to an issue you just created

Even create an issue, and then need to update it? Us too, all the time.

Before, once an issue was created it was buried. You had to use the Issue Switcher or Search.

But today, you can see a link to the issue in the "Issue Created" notification message to bring the issue up:

See it in action:

No published changelogs yet.

Surely Codetree will start publishing changelogs very soon.

Check out our other public changelogs: Buffer, Mention, Respond by Buffer, JSFiddle, Olark, Droplr, Piwik Pro, Prott, Ustream, ViralSweep, StartupThreads, Userlike, Unixstickers, Survicate, Envoy, Gmelius, CodeTree