Flow run graphs highlight tasks with a color that corresponds to their state (green for complete, red for failed, etc). However, tags are another vital piece of metadata, and the only way to see tags today is to click an individual task in the graph and open its detail drawer.
Describe the proposed behavior
The flow graph should include tags so that I can see any user-provided annotations at a glance. There are many ways to do this. Here are a few ideas:
Color code tasks by tag (this would involve a toggle to go between status-based color coding and tag-based color coding)
Show the list of tags under each task name in the graph.
Provide a tag filter so that users can show/emphasize the tasks in the graph that have a particular tag.
Example Use
Some tasks are "business-logic", some are "glue". Being able to separate them visually would be nice. Some tasks might feed into different departments, for example. Or some might enrich data via ML while some enrich via business rules.
If I've built an ETL flow, I might assign tags to identify which tasks are involved with "extract", "transform", and "load", respectively. If we exposed the ability to view tags in the flow graph, I could see at a glance that all of my load tasks are failing (for example).
Prefect Version
3.x
Describe the current behavior
Flow run graphs highlight tasks with a color that corresponds to their state (green for complete, red for failed, etc). However, tags are another vital piece of metadata, and the only way to see tags today is to click an individual task in the graph and open its detail drawer.
Describe the proposed behavior
The flow graph should include tags so that I can see any user-provided annotations at a glance. There are many ways to do this. Here are a few ideas:
Example Use
Some tasks are "business-logic", some are "glue". Being able to separate them visually would be nice. Some tasks might feed into different departments, for example. Or some might enrich data via ML while some enrich via business rules.
If I've built an ETL flow, I might assign tags to identify which tasks are involved with "extract", "transform", and "load", respectively. If we exposed the ability to view tags in the flow graph, I could see at a glance that all of my load tasks are failing (for example).
Additional context
No response