You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This approach modifies the python to generate new svg/html outputs.
When rendering graphviz outputs, for each current output also render a "Bird's Eye View" DAG. The latter collapses all milestones/epics into single nodes. This means for any issue A in milestone X which depends on issue B in milestone Y, the Bird's Eye node X will depend on the Bird's Eye node Y.
Note: This Bird's Eye view can have cycles, eg: issue A in X depends on issue B in Y, and B depends on C in X. I think this is fine (although it's not a DAG) if the Bird's Eye view shows these cycles. That simply indicates those milestones must be concurrent or interleaved. (But it may also suggest we may want to refactor milestones?)
The Super Fancy Approach
This approach modifies the html/svg rendering to allow a user to dynamically switch between the two views.
This could be somewhat generic (if posisble) to work with any graphviz SVG output. It could identify the subgraph containers and calculate the Bird's Eye view then either swap out all of the SVG widgets or perhaps an HTML renderer could have two view containers that it toggles the visibility of.
The text was updated successfully, but these errors were encountered:
#47 (now implemented) does a similar thing for "target issues" with the label C-target. If the milestone bird's-eye view is still desired, it could likely be implemented with similar rendering logic (except that unlike the issue graph which is only not a DAG due to mistakes when adding edges, the milestone relational graph can inherently include cycles).
The Feasible Approach
This approach modifies the python to generate new svg/html outputs.
When rendering graphviz outputs, for each current output also render a "Bird's Eye View" DAG. The latter collapses all milestones/epics into single nodes. This means for any issue A in milestone X which depends on issue B in milestone Y, the Bird's Eye node X will depend on the Bird's Eye node Y.
Note: This Bird's Eye view can have cycles, eg: issue A in X depends on issue B in Y, and B depends on C in X. I think this is fine (although it's not a DAG) if the Bird's Eye view shows these cycles. That simply indicates those milestones must be concurrent or interleaved. (But it may also suggest we may want to refactor milestones?)
The Super Fancy Approach
This approach modifies the html/svg rendering to allow a user to dynamically switch between the two views.
This could be somewhat generic (if posisble) to work with any graphviz SVG output. It could identify the subgraph containers and calculate the Bird's Eye view then either swap out all of the SVG widgets or perhaps an HTML renderer could have two view containers that it toggles the visibility of.
The text was updated successfully, but these errors were encountered: