Skip to content

docs(flaky-tests): document the Jira Data Center ticketing integration - #399

Merged
acatxnamedvirtue merged 1 commit into
mainfrom
tylerbeebe/jira-data-center-ticketing
Oct 10, 2026
Merged

acatxnamedvirtue merged 1 commit into
mainfrom
tylerbeebe/jira-data-center-ticketing

Conversation

@acatxnamedvirtue

Copy link
Copy Markdown
Contributor

Adds flaky-tests/management/ticketing/jira-data-center-integration, the page the Jira Data Center connection form already links to ("View instructions"). Today that link has no page behind it.

Draft until the feature is ready to publish. Jira Data Center support is merged in trunk2 (trunk-io/trunk2#6897 to #7007, with #7013 to follow), but it's behind the showJiraDataCenterTicketing flag. Merge this when the flag goes on for customers, or keep the page's "contact support to turn it on" note if it stays per-org.

What the page covers

  • Requirements: Data Center 10.0+; reachable over HTTPS from the internet; an org-level connection only.
  • The personal access token: a dedicated service account is recommended (Data Center tokens have no scopes), the exact project permissions, and expiry.
  • Connecting: the two-step form, and the fields.
  • The Trunk API: linking tickets needs the site allowlisted on request, matching the note on the form.
  • The rest of the flow: ticket automation, creating and linking tickets, and custom fields, with the supported field types.
  • Security and data access: what Trunk reads and writes, and what it never does.
  • Troubleshooting: every connection error the form can show, and what to do about it.

Also adds a Jira Data Center card to the ticketing index, a pointer from the Jira Cloud page, a mention on Automatic ticketing, and the page to the navigation.

Screenshots

The form images were captured from the trunk2 E2E harness against a mock Data Center site. They're 2x and cropped to the settings content, like the other ticketing pages. The displayed site URL was swapped for https://jira.example.com/jira before capture.

Checks

  • mint broken-links reports the same 33 lines on main and on this branch, and none touch the ticketing pages.
  • scripts/sync-changelog.py --check passes.
  • No changelog entry is included; that belongs with the launch.

🤖 Generated with Claude Code

A page for the self-managed Jira Data Center integration, at the URL the
connection form links to: requirements (Data Center 10.0+, reachable over
HTTPS), the personal access token and the project permissions it needs,
connecting, the Trunk API allowlisting step, automation, custom fields,
what Trunk reads and writes, and the connection error messages.

Linked from the ticketing index, the Jira Cloud page and automatic
ticketing, and added to the navigation.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated
trunk 🟢 Ready View Preview Oct 9, 2026, 11:36 PM

@acatxnamedvirtue
acatxnamedvirtue marked this pull request as ready for review October 10, 2026 00:05
@acatxnamedvirtue
acatxnamedvirtue merged commit 8c2430f into main Oct 10, 2026
3 checks passed
@mintlify

mintlify Bot commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

Docs PR opened: #400

Added a changelog entry announcing Jira Data Center ticketing for Flaky Tests, linked from the changelog navigation and index pages.

This branch was successfully deployed

1 active deployment
staging — 0093c5ee Deployed Oct 9, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant