Skip to content

chore: explain scoped Jira Cloud API tokens - #2443

Closed
be-student wants to merge 2 commits into
pycontribs:mainfrom
be-student:codex/2368-scoped-api-token-docs
Closed

be-student wants to merge 2 commits into
pycontribs:mainfrom
be-student:codex/2368-scoped-api-token-docs

Conversation

@be-student

Copy link
Copy Markdown

Summary

  • document the different server URL required by scoped Jira Cloud API tokens
  • show the api.atlassian.com/ex/jira/{cloudId} client configuration
  • explain how to obtain the browser-facing base URL when constructing issue links

Closes #2368.

Validation

  • uvx sphinx-lint docs/examples.rst
  • Sphinx HTML build completes with the edited page
  • the repository's strict tox -e docs gate reports the same three pre-existing unresolved jira.resources references on upstream/main and this branch
  • git diff --check

This contribution was prepared with AI assistance and validated locally against the repository documentation build.

@be-student
be-student requested a review from a team as a code owner September 6, 2026 07:25
@be-student
be-student requested a review from ssbarnea September 6, 2026 07:25
@be-student be-student changed the title docs: explain scoped Jira Cloud API tokens chore: explain scoped Jira Cloud API tokens Sep 8, 2026
@github-actions github-actions Bot added the chore label Sep 8, 2026
@be-student be-student closed this Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document server= kwarg for dedicated tenant of Jira Cloud, and difference when using Scoped API Token

1 participant