What’s new in Azure DevOps Sprint 158

Sasha Rosenbaum

Sprint 158 just finished rolling out to all organizations and you can check out all the new features in the release notes. Here are some of the features that you can start using today.

Azure Repos: Preview Markdown in Pull Request

You can now see a preview of how a Markdown file will look by using the new Preview button on the Pull Request Files tab. In addition, you can see the full content of a file from the Side-by-side diff by selecting the View button.

Azure Pipelines: Retry failed stages in YAML pipelines

In multi-stage YAML pipelines, you can now retry a pipeline stage when the execution fails. Any jobs that failed in the first attempt and those that depend transitively on those failed jobs are all re-attempted. (Note: you must have the preview feature Multi-stage pipelines enabled)

We are excited to release a preview of the Deployment control on the work item form. This control links your work items to a release and enables you to easily track where your work item has been deployed.

Azure Boards: Hide fields in a work item form based on condition

We’ve added a new rule to the inherited rules engine to let you hide fields in a work item form. This rule will hide fields based on the user’s group membership. For example, if the user belongs to the “product owner” group, then you can hide a developer-specific field.

These are just the tip of the iceberg, and there are plenty more features that we’ve released in Sprint 158. Check out the full list of features for this sprint in the release notes.


Discussion is closed. Login to edit/delete existing comments.

  • Albert Weinert 0

    It would be nice if you be clear in the wording.

    Sprint 158 just finished rolling out to all organizations sounds for me that everything in ready in all organizations. This is not the case.

    I know that the roll out takes some time, but this leads to wrong expectations.

  • Edward Moore 0

    Hey guys,

    The updates to Boards were very useful in Sprint 157/158 so thanks for that! There was a feature request for mermaid and plantuml support – I see that Mermaid is now supported but when should we expect PlantUML diagrams to be renderable? We have hundreds of UMLs that we render using pipelines into docs, it would be much simpler if Plantuml is renderable as is the case in VS Code.



Feedback usabilla icon