Cosmo Auto State

Features

• Create rules to manage state transitions
  • Ability to check that all child work items also matches rules
  • Ability to process rules from the current work item to the top of the tree
• Rule tester to see how rules work and what work items will be updated
• Get started easily by using preset rules. See preset rules

Where does this work?

This extension does not work on all areas where work items are located:

The reason for this is that Azure DevOps does not include contribution types that allows the extension to hook into State changes in these views

Activating the extension

Activation of this extension must be done by a Project or Collection administrator

For this extension to work properly there are a few steps that needs to be taken after installing:

Activation

Activation is done through the Preview Feature "Auto State". This needs to be enabled for each Project this extension should be used in from the Preview Features menu. This feature flag is scoped to individual projects, that means you need to be inside a project for the feature flag to appear. The url should look something like https://dev.azure.com/ORGANIZATION/PROJECT

When you open the modal with all the feature flags the dropdown should have three options

• for me [Your name]
• for this project [Project Name] (This is the one you should select)
• for this organization [Organization Name]

• Rules needs to be configured. The rule editor is found under Project Settings > Extensions > Auto State

Usage

Documentation on rule usage can be found on GitHub

Limitations

• This extension does not work when doing mass updates
• The state must be updated from the work item form for the update to trigger

(back to top)

Contact

If you have generic questions about the project or usage you can make contact in the following ways:

• Submit an issue over at GitHub with the @type/question label - New Issue
• Submit a new question under the Marketplace Q&A section.

(back to top)