Starting your work with a user story in Pipelines

Understanding the new workflow in your Dev sandbox

Busayo Longe avatar
Written by Busayo Longe
Updated over a week ago

We have recently made changes to the Dev sandbox experience.

If you manage your user stories with Jira or Azure DevOps, you will now select your user story as the first step in committing changes into your pipeline.

This feature is now available to you if your team manages work in Pipelines with Jira or Azure DevOps.

This is a UI workflow change only. It does not affect your CI jobs or any part of your Pipeline besides your Dev sandbox. It means that features or branches that are already in progress further down the Pipeline will not be affected in any way.

Note: If you are new to Pipelines, please see this article for a guided walkthrough on getting started with Pipelines.

The previous Dev sandbox view in Pipelines looked like this:

Here, you would start your commit by creating a new branch from main, which you would need to manually name and then you would start your commit (by clicking ‘Compare and commit).

In the new flow, you would be selecting the user story assigned to you in Jira or Azure DevOps as the first step in this commit process:

This user story is then used to create the branch name:

You are also able to skip the user story selection altogether, selecting ‘skip to creating a branch’ takes you to branch name creation:

If you do not have Jira or ADO set up, you are also taken straight to the branch name creation:

The commit process largely remains the same, however, the final step brings you back into the Pipeline:

Here, you could either commit more changes to the active branch or select a different branch to commit changes to:

Or you could create a Pull Request:

Please reach out to our customer support via the Intercom chat if you have any feedback or run into any issues. We’d love to hear from you.

Did this answer your question?