Seqera Platform Feature Requests

It would be helpful to be able to shortcut from the Reports tab directly to Data Explorer, either to download a file that is too big to be downloaded from Reports or to further explore the results directory.

This project will introduce versioning capabilities to Seqera Platform, allowing users to create, save, and reference different versions of pipelines based on their configuration and parameters. Planned Features Automatic Version Tracking Automatic snapshot creation whenever a pipeline is created, modified, or launched with edited versioned parameters Checksum-based tracking for pipeline integrity and provenance All configuration changes preserved in version history Version Management Users with pipeline edit capabilities can assign custom names to snapshot versions Ability to set any named version as the default for launch Option to save completed workflow runs as new named versions Named versions can be reassigned to different snapshots Versioned Parameter Control By default, parameter changes trigger automatic version creation Custom nextflow_schema.json files can define which parameters should not trigger versioning Launch users can modify parameters and automatically create snapshots Version Selection at Launch All users see the default named version in the launch form Users with pipeline edit capabilities can select and launch any version (named or snapshot) Launch users can view and launch named versions from the pipeline details page Launch users create snapshots through parameter modifications but cannot publish named versions Commit ID Tracking Commit IDs are stored alongside branch/tag information for reproducible pipeline execution Users can pin to specific commits or update to the latest branch version Pull latest toggle sets commit ID for dynamic branch tracking Target Users This functionality is intended for bioinformaticians who customise platform pipelines for themselves or their users, applicable to all customers including Enterprise requiring pipeline execution control.

Currently in the Launchpad, when you register a pipeline, there is a Description box. We end up having to write a custom description for every pipeline for the users to read. However, we already have a README.md in every pipeline repo with similar details, and we even have external pipeline docs too. So being forced to re-write a static description here ends up with duplicated docs that can also get outdated easily. I think it would be easier if there was some way that the Launchpad could (optionally?) use the contents of the pipeline repo's README.md file and render it in the Description field instead. So we could just updated the repo's files itself and they would be reflected in the Launchpad, somehow. Or maybe the pipeline README.md could be displayed in a separate box on the pipeline's Launchpad page?