Feature #12517

[Workbench] page with a view of all the top level container requests

Added by Bryan Cosca about 1 year ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
10/31/2017
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Similar to workbench.xxxxx.arvadosapi.com/pipeline instances, I would like a page that has top level container requests. The workbench.xxxxx.arvadosapi.com/container_requests page does not satisfy that because it shows ALL container requests.

When more container requests get run, the top level ones effectively get lost forever unless you remember exactly where it is, because Dashboard only shows the last 12 pipeline instances / top level container requests.


Related issues

Related to Arvados - Feature #12315: [Workbench] on all processes page, add filter to make it possible to exclude sub workflowsResolved2018-02-17

Related to Arvados - Bug #11625: [Workbench] Ensure that running processes are visible on the dashboardNew

History

#1 Updated by Bryan Cosca about 1 year ago

  • Project changed from Arvados Private to Arvados

My current workaround is to name pipelines after some heuristic like issue tracker number so I can filter on that. Maybe there's another filter I can use?

#2 Updated by Tom Morris about 1 year ago

  • Target version set to To Be Groomed

#3 Updated by Tom Clegg about 1 year ago

  • Related to Bug #11625: [Workbench] Ensure that running processes are visible on the dashboard added

#4 Updated by Lucas Di Pentima about 1 year ago

Coalescing #12315, #11625 & #12517 into one UI proposal:

  • Change the “Recent pipelines & processes” panel on the dashboard to “Active pipelines & processes”, only showing the top level processes which are in active state (maybe all of them instead of the first N?)
  • On the “all processes” page, only showing the top level processes (in any state), ordered by descending creation date and adding an checkbox to include the subworkflows, or maybe having the subworkflows already collapsed as subitems of every top level process row.
    • When showing the subworkflows, it may be convenient to reorder them differently? (For example by starting date)

Also available in: Atom PDF