Actions
Feature #4802
closed
[Workbench] UX of pipeline instance Inputs tab needs improvement
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Story points:
-
Description
Currently, the inputs tab for a new instance is very ambiguous. For example, in this pipeline we have to specify picard 3 times in 3 different jobs and we have no idea which jobs those go to, looking at this picture. (Also, I get the question in demos that go "So why is picard being specified 3 times?") I like that the components tab is very helpful that pipelines are split up into jobs and you can see what you change for each job. I was also thinking of a way to maybe remove some of these parameters from the interface so that you don't see every parameter. For example, if they have a default parameter already, we do not need to see these parameters pop up.
Files
Updated by Brett Smith about 10 years ago
- Subject changed from The inputs tab in a pipeline instance could be more helpful to [Workbench] UX of pipeline instance Inputs tab needs improvement
- Category set to Workbench
Updated by Tom Clegg almost 10 years ago
Some workarounds are available:
- Provide better "title" and "description" fields. For example, each "Version of Picard tools to use" could indicate in the description which component it affects, and suggestions about values (other than the default) that are likely to work.
- If a parameter does not provide a description or specify
"required":truethen it does not appear on the "Inputs" tab at all. (It will still be editable on the "Components" tab, though.) If the user is not normally expected to customize a given parameter, this might be more appropriate.
Updated by
Actions