No need to show green dependencies

[nicola]

The bytes of information that I care about looking at an issue is what makes it blocked, not what make it unlocked. When the dependencies turn green, you can avoid showing the green circle (too many circles!)

---

depends on #34

[wking]

On Mon, Nov 21, 2016 at 10:14:11PM -0800, Nicola Greco wrote:

The bytes of information that I care about looking at an issue is what makes it blocked, not what make it unlocked. When the dependencies turn green, you can avoid showing the green circle (too many circles!)

This sounds like “don't show completed cards”, which sounds reasonable to me. Although I don't mind having that be toggle-able either, in case someone does have a use-case for walking the historical graph.

Or maybe we only want to show completed parents (but not deeper ancestors)? The completed parents may have useful information about how the border issue (an issue that is open but which has no open dependencies) is expected to be addressed. For example, maybe the completed parent was “Add a FooBar API”, and the border issue is expected to use that API to complete the problem.

And presumably you'd want to see related issues regardless of their state, since “related” isn't defined clearly enough to allow us to make decisions about it automatically.

[jbenet]

I do care about the completed ones, and want to see them / explore. sure, this can be an option for those who don't.