Flags deep dive: Design handoff files are below quality standards

Modified on Mon, 3 Feb at 12:34 PM

When to use this Flag?

Leverage this flag to get an understanding of all poor quality Figma handoffs associated with build issues in active/planning sprints

Impact:

Process

Classification:

Requirements

Tools:

Figma, Atlassian Jira

Intent:

This feature integrates with Figma to automatically identify handoffs associated with build issues and evaluate their quality against predefined rules/metrics. Design and Engineering managers can set custom thresholds to ensure timely assessments. By proactively identifying low-quality handoffs, we can minimize unnecessary revisions and improve collaboration between developers and designers. The algorithm is executed based on the following rules:

Measures how well components and styles in Figma files conform to the published library.
Assesses the presence of descriptions, prototypes, and highligt texts in Figma.
Evaluates the use of meaningful and appropriately sized names in Figma.
Measures the use of comments and its resolution in Figma.

Configurations:

The weightage for each of the parameters for determining the quality of the design file. In case the parameter is irrelevant, the user can set it to 0 percent.
Define the threshold level for the overall score; hand-off sections with scores below the specified threshold level will result in the flag.
Define the type of sprints to be monitored by the platform (active sprint, planning sprint or all types of sprints).
Enable auto-resolution settings and select "report this flag as an issue in Jira" as the option, this will ensure that a bug is created in Jira for the flag (the bug can be expressed using a chosen issue type per project in the configuration).
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.