Skip to content

docs: Bitrise for Jira app panel project visibility - #327

Merged
zoltan-baba merged 2 commits into
mainfrom
docs-impact/jira-app-panel-project-visibility
Oct 6, 2026
Merged

zoltan-baba merged 2 commits into
mainfrom
docs-impact/jira-app-panel-project-visibility

Conversation

@jp-bitrise

@jp-bitrise jp-bitrise commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

🤖 Agent-authored docs-impact review. Generated from a code change in
bitrise-io/bitrise-for-jira by the docs-impact-review skill. Needs human verification
before merge
- this is the publish gate.

Source change: CI-6481 - restrict the Bitrise builds section to selected Jira projects. Code: bitrise-io/bitrise-for-jira#37 (display condition) and #38 (admin-page project picker).

✅ Feature is live. Confirmed by Jeremy: CI-6525 (production release) has shipped. It is a major app version, so existing installs still get the picker only after a Jira admin approves the update, which the docs describe.

Changes for this code change

  • bitrise-for-jira-app.mdx: new section "Limiting the Bitrise builds section to specific Jira projects" (the Connected Jira projects picker, Save panel visibility, empty selection = every project).
  • bitrise-for-jira-app.mdx: new optional row in the "Setup at a glance" table.
  • bitrise-for-jira-app.mdx: note that the setting affects only the Bitrise builds section, not the Builds tab of the development panel, and is separate from Connected Bitrise projects; important box on approving the major update.
  • bitrise-for-jira-app.mdx: troubleshooting bullet for the section missing in one Jira project.

Pre-existing drift fixed

  • bitrise-for-jira-app.mdx: UI labels corrected to match the app (Bitrise API token, Connected Bitrise projects; the page had title-cased the last word).

What a reviewer must verify before merge

  • The documented behavior matches what actually ships (and is enabled, not flag-gated off), including that existing installs need admin approval of the major version
  • The Builds tab of the development panel is unaffected by the setting (inferred from the code: the display condition is only on the jira:issueContext module)
  • Slugs / partials / sidebar order render correctly (npm start in the docs repo; not run by the agent)
  • No screenshots or version numbers went stale (consider adding a screenshot of the new Connected Jira projects section)
  • API reference pages were correctly left untouched (not applicable: no Bitrise API changes)

@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@zoltan-baba
zoltan-baba merged commit 70f6c53 into main Oct 6, 2026
5 checks passed
@zoltan-baba
zoltan-baba deleted the docs-impact/jira-app-panel-project-visibility branch October 6, 2026 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants