Flags deep dive: Specification changes observed

When to use this Flag?

Leverage this flag to catch any changes made on the design document, requirement document or tech specification document associated with a planned or active build issue. 

Impact:

Documentation

Classification:

Requirements

Tools:

Atlassian Jira, Figma, One Drive, Google Drive, Confluence

Intent:

This AI flag checks if there are changes in the design files, tech spec documents, and requirement documents associated with your active build issues in the project management tool (e.g. Jira) and highlights them immediately. Often these changes are either unnoticed or noticed too late in the build cycle which causes changes in the codebase. The intent of this flag is to avoid such code build or code changes when the specifications are  changing during build.

Configuration:

1. Define the type of sprints to be monitored by the platform (active sprint, planning sprint or all types of sprints).
2. Enable auto-resolution settings and select "Move issue(s) to backlog" as the option, this will ensure that the platform automatically moves all issues with specification changes to the backlog.
3. Enable this as a compliance flag if you think this can have an impact on your internal or external regulations; this will ensure the visibility of all the artefacts violating this flag in the compliance status report.