Add warning about unsupported Jira scoped API tokens#3082
Open
HuyPhanNguyen wants to merge 2 commits intomainfrom
Open
Add warning about unsupported Jira scoped API tokens#3082HuyPhanNguyen wants to merge 2 commits intomainfrom
HuyPhanNguyen wants to merge 2 commits intomainfrom
Conversation
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.
Background
Jira Cloud scoped (granular) API tokens require a different API base URL (
https://api.atlassian.com/ex/jira/<cloudid>/rest/api) and authentication method than what Octopus currently supports. This has been reported by two customers (ZD #180265, ZD #197530) but the docs don't mention the limitation.Results
Adds a warning to the Jira Cloud integration docs clarifying that scoped API tokens are not supported and users should create classic (unscoped) tokens.
fixes FD-174
Before
No mention of scoped token limitation — customers discover it only after setup fails.
After
Warning block appears alongside the existing API token note, telling users to use classic tokens.
How to review this PR
Single file change, 5 lines added.
Files changed:
src/pages/docs/releases/issue-tracking/jira.md— added warning block after the existing "Jira Cloud only supports API tokens" notePre-requisites