Enable user-defined patterns for resource names (specifically Runs) | Voters

Enable user-defined patterns for resource names (specifically Runs)

acknowledged

Drew DiPalma

Currently, Run names are auto-populated by a random two-word string. It would be helpful for organizations if naming conventions for resources in Seqera Platform (such as Runs) could be enforced via a pattern/policy defined by an administrator.

April 17, 2024

Rob Newman

Merged in a post:

Custom Naming of Pipeline Runs

Canny AI

It would be beneficial to have the ability to custom name pipeline runs in Seqera to easily identify specific runs, especially when dealing with multiple datasets.

March 3, 2026

Yinmn blue Partridge

I would just like to be able to enforce that the name HAS to be set to something.

Rob Newman

Merged in a post:

Configurable Default Workflow Names

Canny AI

I would like the ability to configure default workflow names to automatically include specific metadata, such as the tool name and date-time, instead of the current default naming convention.

September 29, 2025

Rob Newman

marked this post as

acknowledged