General

Way of working

This setting is crucial for linking tasks with their respective parent work items. While it can be disabled, doing so may reduce the tool's effectiveness. Enabling this ensures proper task check-in alignment.

Code Markup

This is the initial default comment if no other is set. Originating from Joris de Gruyter’s blog on branching strategies, it inspired this plugin's creation. Note: This feature is slated for removal in upcoming releases as custom comments become more prevalent.

Branch validation

This experimental feature attempts to align the developer's current branch with a predefined branch name. It’s advisable to disable this feature if it does not align well with your repository's structure. Note: A custom branch field must be created in your work items for this to function effectively.

Activity validation

This is used to decide whether a work item should be validated as a development task, a common way of working with DevOps is to attach different tasks as children to a work item of the Requirement Category. Not all tasks should be validated in the development process in Visual Studio. Very often the Activity field fits this purpose well, the values to compare can be setup in DevOps.

The option to show a warning if the developer isn’t assigned to a task is used to reduce the risk of checking in on a task assigned to someone else.

Telemetry

It is recommended to keep this feature enabled as it aids in identifying and resolving issues swiftly, thereby enhancing the tool's development