Skip to content

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

Draft
samgutentag wants to merge 1 commit intomainfrom
sam-gutentag/jira-custom-fields-docs
Draft

docs(flaky-tests): Jira custom fields now available to all users#530
samgutentag wants to merge 1 commit intomainfrom
sam-gutentag/jira-custom-fields-docs

Conversation

@samgutentag
Copy link
Copy Markdown
Member

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

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

…o general availability

Custom field configuration is now available to all users. Documents the
new per-issue-type field configuration UI, supported input types, and
user override behavior at ticket creation time.

Pairs with trunk-io/trunk2#3453.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@trunk-staging-io
Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

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