Flags deep dive: Related analytics stories are missing for build issue

Modified on Thu, 6 Mar at 5:05 AM

When to use this Flag?

Leverage this flag to get an understanding of all the UI build issues that don't have associated analytics stories

Impact:

Feature

Classification:

Requirements

Tools:

Atlassian Jira

Intent:

The intent of this flag is to connect to project management tool (e.g. Jira), unearth all the UI build issues that are being executed which don't have reference analytics stories. The actual requirements may either exist in the system (and not may be linked) or the actual requirements may not exist in the first place.

If it's the former, then this flag ensures that the systems of records (Jira) represents the source of truth represented in the product being built by the team.
If it's the latter, then this flag enables the Engineering lead/manager to align with the Product lead and fix the issue.

Configuration:

Define the type of sprints to be monitored by the platform (active sprint, planning sprint or all types of sprints).
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.