User should be able to start a new run from the pipeline page.

[Ark-kun]

No description provided.

[yebrahim]

I agree this would be nice to have.
@ajayalfred what do you think?

[ajayalfred]

It's a valuable suggestion.
I would like to make the decision to add this action after doing some usability testing on post-launch usage patterns and user workflows before adding to the pipeline page. The feedback we get gather will take out any guesswork and help us better understand users' mental model.

[Ark-kun]

What is the intended use of an uploaded pipeline?

The user has uploaded the pipeline. Now what? We should try to avoid workflow dead-ends.

There is only one action that the user can ultimately do with a pipeline which is to start a run (possibly, recurring). It's confusing when the pipeline page does not allow the user to perform this action.

[ajayalfred]

That action is accounted for with the 'Start experiment' button which guides the user through creating a new experiment and run.

[Ark-kun]

Do we want the users to create an experiment for each run?

What's the typical number of runs per experiment and experiments per pipeline did we estimate during the planning stage of the "experiments" feature?

[ajayalfred]

There is no real meaningful way of estimating that number as a user can use a pipeline to create any number of runs and experiments. The idea was to give the user maximum flexibility in creating experiments as they see fit.

Although, your suggestion is a valid one - we'll be testing the current experience and identifying potential optimizations. Starting a run without having to create an experiment seems like a viable optimization, and we'll make this change after gathering feedback from user studies.

[rileyjbauer]

@ajayalfred, since there is no "Create experiment" button on the Pipeline list page, should we instead direct the user straight to the Pipeline Details page of the pipeline they just uploaded?

Additionally, we've had a few requests already for a "Create experiment" button from the Pipeline list page itself.

[ajayalfred]

Redirecting to pipeline details page after upload sounds good. That's usually the most common action done after uploading, so makes sense to optimize.

I'm hesitant to put a 'Create experiment' button in the list since it will be disabled until a user selects a pipeline, and it only works for single selection. If you count the number of clicks, that's exactly the same as clicking the pipeline link and clicking 'Create experiment' from the details page. So the additional button on the list page is not an optimization and doesn't improve the experience.

What we could do however is add an icon button in the pipeline list row to start an experiment. I'll create and self-assign issue to track this exploration.

[ajayalfred]

#256

[ajayalfred]

We discussed and agree this is valuable to have. I am creating a design spec for this and the associated workflow changes.