Flags deep dive: Tasks not planned to meet benchmarks

Modified on Mon, 3 Feb at 11:50 AM

When to use this Flag?

Leverage this flag if you have set expectations on how you want your tasks to be defined on Jira for different issue types and want to catch any deviations.

Impact:

Process

Classification:

Requirements

Tools:

Atlassian Jira, One Drive, Google Drive, Confluence

Intent:

This is an AI flag that automatically compares the development issue planned in the project management tool (e.g. Jira) against predefined benchmarks and does the following:

Identifies inconsistencies vis-a-vis the specified benchmarks.
Suggests necessary task additions based on those inconsistencies.

By automating this process, Scrum and Engineering managers can avoid the time-consuming task of manually reviewing each issue for completeness OR worse, discovering it very late into the sprint. This helps prevent missing tasks from escalating into project mismanagement and poorly executed builds.

Configurations:

Define the type of sprints to be monitored by the platform (active sprint, planning sprint or all types of sprints).
Define the benchmarks for different types of builds by specifying links associated issues that represent the best quality UI build, API build, Backend build and Database build.
If it includes build issues in the planning sprint then how much further in time should the platform consider to analyze planning sprints.
Further, it requests the user to select the type of issues that need to be monitored by providing the link against the issue type of choice.