Component Release QA

Component Release QA Support

Contact

Email exportpreflightsupport@gmail.com with “Component Release QA” in the subject. This address is shared with another product; the subject helps us route your request. Please write in English or Japanese. For paid Community resources, Figma’s Creator Agreement requires a support email and responses to customer inquiries within three business days; the publisher must maintain this support coverage.

Quick start

  1. Select one local Component Set in Figma Design—not an individual Component, instance, or remote library component.
  2. Open Component Release QA. Check the Component Set name, variant count, axes, and values.
  3. Click Add required combination. Enter one value for every axis; future custom values are allowed. Add only combinations your team requires.
  4. Enable any optional Quality Rules, confirm the target and conditions, and click Run QA.
  5. Review the counts and diagnostics. A missing variant jumps to its parent Component Set; other diagnostics jump to the relevant node where available.
  6. Save a named profile if you want to reuse the requirements. After editing the design, re-scan and confirm before running again.

Understanding results

Free and purchased features

The free preview includes setup, QA, all diagnostic counts, the first five diagnostic details, and profiles. The preview has no time or run limit. Purchase unlocks all diagnostic details and full CSV export. Figma handles payment; the planned launch model is a US$10 one-time purchase. The actual price is shown by Figma checkout.

If the plugin cannot verify payment status, it does not unlock paid features. Use the same Figma account used for purchase and click the payment-status refresh button. Do not send passwords, card details, payment tokens, or Stripe information to support. Use Figma’s official purchase support for transaction and refund questions.

Troubleshooting

If the UI does not recognize a set, select exactly one local Component Set and re-scan. If the target or axes changed, re-enter or explicitly reload compatible conditions and confirm them.

If Figma displays conflicting variant values, fix those conflicts yourself in Figma. Figma may block the metadata API for that set; the plugin will show Incomplete instead of guessing. The plugin does not edit or repair nodes.

Description warnings are advisory. Check the actual description fields: Figma’s API can return missing or stale descriptions. Either a nonempty plain-text or Markdown description is accepted when retrieved.

Profiles are saved locally through clientStorage, not synced to another computer or shared with teammates. Inputs and Quality Rules are not automatically saved. A profile stores requirements, not optional Quality Rules or the last QA report. Use Save profile or Update profile explicitly.

CSV export requires a purchase and a current QA result. A change to the target, requirements, rules, or document invalidates old results. Re-scan and Run QA again. Check the local save dialog when downloading from Figma Desktop. If your spreadsheet application misreads the file, import it explicitly as UTF-8, comma-delimited, with double-quote text delimiters.

Reporting a problem

Include the plugin version, Figma Desktop or browser version, macOS/Windows version, reproduction steps, and expected versus actual behavior. A small sanitized screenshot is useful. Please remove design names, node IDs, confidential data, and account information you do not want to share. Do not email an entire design file unless you choose to do so after discussing a minimal reproduction.