Conditional parameter visibility in the pipeline launch form (show/hide fields based on other parameter values)
acknowledged
G
Geographical Reptile
When launching a pipeline, some parameters are only relevant depending on the value of another parameter. Add support for conditional parameter visibility in the launch form, where selecting a value in one field can reveal or hide dependent fields. This would reduce clutter and make the launch interface more intuitive for complex pipelines with many configuration options.
Rob Newman
Merged in a post:
Dynamic parameter lookup / dependent dropdowns in the pipeline launch form
C
Cloudy Llama
When launching a pipeline, some parameters depend on the value of other parameters (e.g., selecting a genome assembly should filter available annotation files, or selecting a project should populate available sample lists). Currently, all parameter values must be statically defined in the schema. Add support for dynamic parameter lookup — where selecting a value in one field triggers an API call or lookup to populate dependent fields — so users see only valid, context-appropriate options without manual entry.
P
Prospective Puma
We work with multi-step bioinformatics pipelines that require conditional inputs — certain parameters only make sense depending on choices made earlier in the form. Without dynamic schemas and conditional field visibility, users are presented with irrelevant options, which increases the chance of misconfiguration. This feature would significantly improve the launch experience for complex workflows.
Rob Newman
updated the status to
acknowledged
Phil Ewels
This is dependent on having a syntax to support this within Nextflow Schema files. I've created an issue to track that first part here: https://github.com/nf-core/tools/issues/3320