docs(flaky-tests): document the Asana ticketing integration

[acatxnamedvirtue]

Documents the Asana ticketing integration shipped in trunk2 #5044–#5066.

Adds flaky-tests/management/ticketing/asana-integration.mdx and folds Asana into the pages that previously named only Linear and Jira — the ticketing index, automatic ticketing, the nav, and the top-level product index. Modeled on the Linear page so the three read the same.

The two things that actually differ

Asana is not shaped like Jira or Linear, and the page leads with that rather than burying it:

• Statuses are project sections. Asana has no workflow states, so a ticket's status is whichever column it sits in. And because a section carries no built-in meaning, Trunk can't guess which of your columns means "done" — both the close and reopen dropdowns list every section and you choose. A column named Shipped works as well as one named Done.
• Closed means completed and in the close section. Asana tracks its completed checkbox separately from sections, so a half transition isn't a close: a task ticked complete in another column isn't closed, and neither is a card dragged to the close column without being completed. That's exactly the state Trunk writes when it closes a ticket, so anything Trunk closed always reads back as closed.

Things a reader would otherwise hit by surprise

• Connecting is two steps — until the token is saved the form shows only the Asana Connection section, and the Configuration section holding Workspace and Project isn't rendered at all, because Trunk can't list workspaces without a working token.
• An Asana personal access token has no scopes; it acts as the person who made it, so that person authors every automated ticket and comment. Flagged with a <Note> suggesting a service account.
• Which custom field types are supported, and why formula and custom-ID fields are absent (Asana calculates them and rejects writes).
• Changing the project clears every field default, because custom fields belong to a project.
• A linked task must be in the configured project — Trunk reads status from that project's sections and would have none otherwise.
• Linking takes the task ID, with an example of where to find it in the URL.
• Why a linked ticket displays as "Ticket" rather than a task name (the gid is opaque, and the generated name truncates identically on every ticket).

Conventions

Followed CONTRIBUTING.md: → navigation paths with bolded labels, the Navigate/Open/Click/Select verbs, and <Note> for "you must act on this to get a correct result" rather than <Warning> (nothing here is a hazard).

Changelog entries were left alone — they're dated records of what was true at the time.

Screenshots

Connect-form and create-ticket screenshots are included as light/dark pairs, matching the sibling pages. The connect-form shot sits below the setup steps rather than above them, since it shows a fully connected integration and the surrounding text describes what is not on screen before the token is saved.

The ticketing index card also has a thumbnail now. The supplied asana.png was 256×256; jira.png and linear-v2.png are both 1600×1000, so a square image would have rendered at a different height and broken the card row. I scaled the mark up and padded to 1600×1000 in the asset's own background colour, which puts the mark at roughly the same proportion of the canvas as Linear's. The source tile's pale pink background was replaced with white to match the other two. A flat colour swap would have left a pink fringe on the circles' antialiased edges, so each pixel's blend factor against the original background was recovered and the mark recomposited over white — the mark-free areas of the canvas are now pure white with no halo.

One follow-up

• No changelog entry. The feature ships behind a flag and isn't generally available, so announcing it now seemed premature. Worth adding when the flag opens up — changelog/2026-07-31-flaky-tests-automatic-ticketing.mdx is the closest model.

Verification

docs.json parses and the nav entry resolves; every relative link in the new page is one already used by the Linear page. The mint CLI isn't installed here, so I did not run a local preview build.

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
trunk	🟢 Ready	View Preview	Aug 11, 2026, 2:05 PM

[mintlify]

Docs PR opened: #312

Added an August 11, 2026 changelog entry announcing the Asana ticketing integration for Trunk Flaky Tests.