Add a new idea Subscribe
Status Shipped
Categories Features
Created by Guest
Created on May 7, 2015

RELATED IDEAS

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-189 Dependency Tree for features.

Feature dependency graph Merged

It is possible to visualize feature dependencies as part of the release Grantt diagram, but it would also be very helpful to view parking lot features, or features cross-release, as a graph with nodes and directed edges symbolizing feature dependencies. Here's an implementation of this idea in JIRA: https://marketplace.atlassian.com/plugins/com.kitologic.pathfinder

Visualizing unfinished features and their dependencies across all products is very important for us to inteligently plan future releases.

  • Emily Slattery
    Reply
    |     Jul 25, 2016

    It would also be helpful to see some sort of visual icon on the scorecards denoting dependencies as well. 

  • Guest
    Reply
    |     May 29, 2016

    I agree that it would be very useful to be able to see feature dependencies in this way.  Some sort of highly visual DAG (directed acyclic graph) that represents the relationships between features, including features across products.  An example from the IT realm might be a feature to build a new database platform within your IT infrastructure group, which is then going to be consumed to enable new features in multiple other products.  It would be great to have a graph that quickly shows that there are features in three products waiting to leverage that new database platform.  And all of these features might currently be in parking lots, so we need to see this graph before we have a release planned, and of course across products.  Casual.pm is built around this sort of view, for one reference point.

    If you think about this from the point of view of a single feature, it would be easy to show its DAG of ancestors and descendants, even across products.  It's more interesting to think about how best to show the collection of DAGs for a whole set of features (e.g. everything in a parking lot, or everything in a particular release or whatever custom set of features you've selected).