Flags deep dive: Aging build issues

Modified on Mon, 3 Feb at 12:34 PM

When to use this Flag?

Leverage this flag to get visibility on aging & hidden build issues in the Jira backlog.

Impact:

Process

Classification:

Feedback

Tools:

Atlassian Jira

Intent:

The intent of this flag is to connect to Jira and unearth all the aging build issues from the project management tool's (Jira) backlog that needs the attention of the Scrum team for their future sprint planning; these bugs could be important technical bugs or rescheduled build topics or bugs created based on evidence generated by Cubyts for Technology drifts. Cubyts augments this data with priorities, the type of work (e.g. UI, backend, etc.) to provide the most relevant context to aid decision making.

Configuration:

Select the issue type that must be used to compute the aging characteristics.
Define the age of the issue e.g. flag the issue when it crosses the threshold set in the backlog age.
Enable auto-resolution settings and select "Move issue(s) to sprint" as the option, this will ensure that the platform automatically moves all issues (breaking the threshold) the next planned sprint.
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.