Enhanced Task Table in Workflow Runs
acknowledged
B
Brass Wildcat
In each workflow run, there's a table of individual tasks within the "Tasks" section. Some workflow runs may involve thousands of individual processes, and enabling search and filtering by process, tag, status, and more would greatly assist users in managing and analyzing their tasks, similar to how you can search and filter the list of workflow runs.
The current Task widget presents a large amount of data in a confined space. Users must navigate the table through pagination, which can be cumbersome. Additionally, the absence of sorting options in the table can prevent effective pattern recognition.
To address these issues, we propose several enhancements. Firstly, we recommend incorporating an expand/collapse feature for the table, allowing users to view it in full-screen mode for a more comprehensive and user-friendly experience. Additionally, where supported, we suggest enabling sorting of table columns. Finally, we propose the implementation of a data export to csv.
These improvements will enhance the user experience by providing more effective ways to manage and analyze the data associated with individual tasks within workflow runs.
Rob Newman
Merged in a post:
Add copy to clipboard button for task native IDs
Esha Joshi
In the 'Tasks' table for a run on the Platform, we're able to retrieve the native ID for the task which usually corresponds to the associated job ID. This ID is often used for troubleshooting failed tasks in the appropriate cloud provider (i.e. AWS, GCP).
Currently, users need to manually highlight and copy these native IDs by precisely highlight the entire ID string or in the case of tasks run on Google Batch, the partial string delimited by a '/0/' character.
This process can lead to partial or incorrect copying of the ID, resulting in user frustration and potential errors in subsequent tasks.
To enhance user experience and improve efficiency, I propose adding a "Copy ID" button/icon next to each ID field, allowing users to copy the ID with a single click.
F
Fellow Bee
About sorting, it's not useful when you have >> thousands of record. It's key to improve searching (look at gmail for example)
F
Fellow Bee
This effort should include a redesign of the table UI. The current one was inherited from an OSS component in the early days.
Rob Newman
Merged in a post:
Expose the reason why a task was terminated
B
Brass Wildcat
The tasks table could provide a clearer way to know the reason why a task execution failed, other than the exit status, which may not provide actionable information.
Extending both the tasks table and the task detail dialog, to include the error reason string could make useful troubleshooting information more accessible. This information is usually exposed by a cloud batch scheduler, e.g., AWS Batch.
Rob Newman
acknowledged
B
Brass Wildcat
Merged in a post:
Features: Display more tasks, filter by sample name
T
Teal Gerbil
Features:
- Show aggregate stats below the processes, show full name of processes.
- Fit tower ui to screen, reducing white space enabling better visibility.
3.Display more tasks not limited by 10 when running pipelines
- Drop down filter tasks by sample name
B
Brass Wildcat
Merged in a post:
Enable advanced search and filter for workflow run Tasks
Rob Newman
In each individual workflow run, there is a table of individual tasks in the "Tasks" section. It would be great to enable advanced search and filter features here.
A run might have thousands of individual processes, and it would be very helpful to search and/or filter by process, tag, status, etc in a similar way to how you can search and filter the list of workflow runs (see attached screenshot).