Update supported Jira field types to match the implementation - #724
Merged
Conversation
Labels, cascading select and searchable multi-selects are supported, so the page no longer lists them as missing. Documents the read-only placeholder for fields Jira returns without allowed values, and the user/security level/time tracking types that still have no control. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Deploying docs with
|
| Latest commit: |
ac257a6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0dc1147b.docs-c7r.pages.dev |
| Branch Preview URL: | https://issue-5891-jira-field-types.docs-c7r.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rewrites the Supported Jira Field Types section of the Jira integration page so it matches what
create-issue.jsactually builds onmaster, verified live on beta (projectintegration-with-jira, Jira projects TIF and TB).<field is not available, value can't be set>shown when Jira returns a field with no allowed values — this behaviour was undocumented.user,securitylevelandtimetrackingfields (Owner, Security Level, Original Estimate) still have no dedicated control and must be set in Jira after the issue is created.The
## Supported Jira Field Typesheading is kept verbatim —advanced/jira-plugin/jira-issue.mdlinks to its anchor.Closes https://github.com/testomatio/testomatio/issues/5891
Test plan
npm run buildpasses/integrations/issues-management/jirarenders and the three subsections read correctly/advanced/jira-plugin/jira-issueto#supported-jira-field-typesstill resolves