It's very strange that such a powerful and mature Ci doesn't have UI for triggering workflows yet. Releasing is a naive job that can be triggered from UI - just specifying "patch|major|minor" parameter and run the workflow to make a new release.

The only workaround now is to create a tag and have a workflow get triggered on this - but this is manual and error-prone work...

Links below for related ideas don't work.

Here are the new links:

Do we have a timeline for this feature? It helps people who will be planning to migrate to CircleCI if this feature is there. Every other CI tool has this feature.

I know this is very late, but for the rollback workflows / jobs you could have an environmental variable store version you desire to roll back to.

I think Buildkite makes an awesome job with allowing user input at any time. This is exactly what I need: https://buildkite.com/docs/pipelines/input-step#select-input-attributes

Related ideas:

This would be extremely helpful for rollback situations!

We currently use a CircleCI workflow for deploying to production upon approval, which works great – except for rollback... when we've discovered a bug that was introduced more than one deployment ago, the only option we have is a very manual process for deploying a specific older version. If there was a way to specify input arguments for a manual workflow, then we could easily use a CircleCI workflow to rollback to arbitrary deployments!