Hi,
I like the idea of the tree view but in practice it gets very unwieldy very fast in a large workspace so I never use it.
Would it be possible to add a view mode where a local tree is visualized? say everything within two (or n) nodes of the selected job? This would be very helpful for visualizing the connectivity of a complicated workflow.
Often when I want to find the inputs or clones of a given job it involves a lot of scrolling and hunting through similar looking jobs - this would make that a lot easier I think. Even without tree view - just being able to quickly show all the jobs that are directly (or maybe one step removed from) the currently selected job, while hiding everything else, would be extremely useful.
Cheers
Oli
3 Likes
Hi @olibclarke,
That’s a great idea - we’ll add it to our to-do list!
- Suhail
2 Likes
This would still be very handy - being able to group jobs is great, but has a number of limitations in practice. Often I just want to view a job and the direct descendants/ancestors - being able view a local tree centered on the selected job(s) would be very handy, and would also be useful for making workflow figures (to remove irrelevant jobs from the view)
EDIT:
In a more limited implementation, this could be implemented as a “view local tree” option in the sidebar, to just show the job with parents and children as a local tree?
Hi @olibclarke,
We are looking at ways to improve the intelligibility and management of very large workspaces, and this type of concept is something we have been ideating on.
So, to make sure I understand your use case and concept, in this case the idea would be to select all parent/child nodes within n nodes of the initially selected job, and then show a new tree with only those jobs in it?
Would your general use case for a feature like this be to filter a subset of jobs in order to visualize their connections and/or find and select a specific ancestor/descendent, and then clear the filter, or would you be expecting to continue processing over an extended period of time with this subset?
- Kelly
Hi Kelly,
So, to make sure I understand your use case and concept, in this case the idea would be to select all parent/child nodes within n nodes of the initially selected job, and then show a new tree with only those jobs in it?
Yes exactly this!
Would your general use case for a feature like this be to filter a subset of jobs in order to visualize their connections and/or find and select a specific ancestor/descendent, and then clear the filter, or would you be expecting to continue processing over an extended period of time with this subset?
More the former than the latter.
Cheers
Oli
@olibclarke ,
Thanks for clarifying further.
I will record this in our tracker to help inform the direction of our current ideation around rendering sub-trees.
- Kelly
1 Like
