docs(flaky-tests): Jira custom fields now available to all users

[samgutentag]

Summary

Updates the Jira integration docs to reflect that custom field configuration is now available to all users, replacing the Enterprise-only gating and sales contact call-to-action with documentation of the actual configuration UI.

Source

• trunk2 PR: https://github.com/trunk-io/trunk2/pull/3453
• Engineering author: @acatxnamedvirtue (Tyler Beebe)

Files changed

• flaky-tests/ticketing-integrations/jira-integration.md — replaces "Enterprise Feature" section with documentation of the custom field configuration UI, supported input types, and user override behavior

Open questions

• Are there any screenshot assets available for the new custom field UI in the settings form and create ticket modal?
• Should the supported field type table be adjusted based on what's actually exposed in production?

Test plan

• Preview in GitBook change request
• Verify accuracy against trunk2 PR diff (trunk-io/trunk2#3453)
• Check for broken links

[trunk-staging-io]

😎 Merged successfully - details.

[claude]

Claude finished @samgutentag's task in 1m 35s —— View job

---

PR Review

• Gather context (read changed file and diff)
• Review for typos, grammar, and formatting
• Review for documentation best practices
• Post inline comments and final summary

---

Overall this is a clean, well-written doc update. The new content accurately replaces the old Enterprise-gating section with clear UI-driven instructions. A few minor polish items flagged as inline comments:

Line	Issue	Severity
104	"create ticket modal" not bolded — UI element names should use bold per doc conventions	Minor
110	Table header says "Jira schema" but preceding sentence says "Jira field schema" — inconsistent	Minor
125	Comma-separated inline code run is hard to scan — a bullet list would be cleaner	Minor
129	"create ticket modal" not bolded — same as line 104	Minor

No blocking issues. All findings are minor style/consistency nits.

[github-actions]

Auto-approved: Claude code review passed.

[samgutentag]

Triage status (2026-05-05): up to date with main. Needs review before merge.

[claude]

Claude finished @samgutentag's task in 1m 6s —— View job

---

PR Review

• Gather context (read changed file and diff)
• Review for typos, grammar, and formatting
• Review for documentation best practices
• Post inline comments and final summary

---

This is a re-review after the latest sync with main. The PR content itself is unchanged since the previous review — the new commits are merge commits from main. The four minor style nits I flagged previously still apply and remain inline on the PR:

Line	Issue	Severity
108	"create ticket modal" not bolded — UI element names should use bold (and the modal name appears to be Create Jira Ticket, per line 91)	Minor
114	Table header says Jira schema but the preceding sentence (line 112) says "Jira field schema" — wording should match	Minor
129	Comma-separated inline code run is hard to scan — a bullet list or code block would be cleaner	Minor
133	"create ticket modal" not bolded — same as line 108	Minor

No new issues introduced by the merge. No blocking concerns — all findings are minor style/consistency nits. The doc accurately reflects the trunk2 PR (trunk-io/trunk2#3453) and reads cleanly.

Fix all four nits →
• Branch

[github-actions]

Auto-approved: Claude code review passed.

[samgutentag]

Verification status (2026-05-06): live

Verified: customers can use this. Ready to publish.

• Eng PR: trunk-io/trunk2#3453 (merged 2026-04-06)
• Linear ticket: none referenced in PR body
• Flag: none. Diff has no useFeatureFlag, useFlag, SHARED_FLAGS, or LaunchDarkly references. The PR removes the prior Enterprise gating outright; it does not gate behind a flag.
• Signals: merge commit present on main. The PR explicitly states it replaces an Enterprise-only feature with availability for all users, which is consistent with no flag gating.

Note: PR is currently in draft. Open questions in the body (screenshots, supported field types) should be resolved before merging.

Suggested next action: get a technical review from @acatxnamedvirtue, fill in screenshots if available, then mark ready and merge.

[claude]

Claude finished @samgutentag's task in 2m 13s —— View job

---

PR Review

• Gather context (read changed file and diff)
• Review for typos, grammar, and formatting
• Review for documentation best practices
• Post final summary

---

This PR was just marked ready-for-review. The doc accurately reflects the trunk2 PR (trunk-io/trunk2#3453) and reads cleanly. However, the four "Applied." replies on the previous inline comments do not appear to match the file content on this branch:

Line	Status	Note
108	Still present	create ticket modal is not bolded (should be Create Jira Ticket modal, matching line 91)
114	Still present	Table header Jira schema does not match preceding sentence wording Jira field schema
129	Still present	Comma-separated inline code run; bullet list (*) would be cleaner
133	Still present	create ticket modal is not bolded (same as line 108)

The branch HEAD on sam-gutentag/jira-custom-fields-docs is 9349198 and the file blob still contains the original wording — the suggestions appear to have been acknowledged but not committed/pushed. If you used GitHub's "Commit suggestion" UI, double-check the commits landed on this branch; otherwise the local edits may need to be pushed.

No new issues to flag beyond the four already-threaded ones, so I'm not duplicating the inline comments. None are blocking — they're consistency nits.

Apply the four nits →
• Branch

[github-actions]

Auto-approved: Claude code review passed.