Flags deep dive: Development landscape deployment pending for build issue

Modified on Tue, 4 Mar at 8:19 PM

When to use this Flag?

Leverage this flag to get an understanding of all the build issues in the active sprint that have not been deployed in development landscape (at least once) for the duration of the sprint.

Impact:

Process

Classification:

Code

Tools:

Atlassian Jira, Jenkins

Intent:

This flag is applicable for companies that follow the Github model of development which mandates frequent deployments of the code in the lower environment (development environment) for validation (by the author of the codebase) before sending out the code for Feature testing (by the QA team).

Configuration:

Define at what point in an active sprint should this issue be surfaced.
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.