Skip to content

Jira Cloud: describe starting one conversation with several repositories - #1050

Draft
ak684 wants to merge 1 commit into
mainfrom
alona/jira-cloud-multi-repo
Draft

ak684 wants to merge 1 commit into
mainfrom
alona/jira-cloud-multi-repo

Conversation

@ak684

@ak684 ak684 commented Oct 29, 2026

Copy link
Copy Markdown
Contributor
  • I have read and reviewed the documentation changes to the best of my ability.
  • If the change is significant, I have run the documentation site locally and confirmed it renders as expected.

Summary of changes

The Jira Cloud page told users to mention exactly one repository. With OpenHands/enterprise#1085, a Jira Cloud issue or comment can name several repositories and OpenHands starts one conversation with all of those it can access (up to ten), comment mentions first. This updates the "Start OpenHands from an issue" section to describe that and the reply, and replaces the "multiple repositories were found" troubleshooting entry with the "Could not access any of the mentioned repositories" one.

This should merge with or after the enterprise change ships.

@mintlify

mintlify Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
all-hands-ai 🟢 Ready View Preview Oct 29, 2026, 7:18 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@ak684

ak684 commented Oct 29, 2026

Copy link
Copy Markdown
Contributor Author

@OpenHands /codereview-roasted

Review exactly commit 94aeb24. If the PR head changes, report that and do not approve another commit. Review only: do not push code, merge, deploy, or change attribution. Check correctness, regression coverage, and whether the PR validation claims match the evidence. Keep code comments short. Post the substantive review and link it in your completion message. End the substantive review with these plain lines (no code fence), choosing one verdict:

REVIEWED_HEAD: 94aeb24
REVIEW_REQUEST: 6a3305eb8dad4704b0807c285256edcf
VERDICT: APPROVED

Use VERDICT: CHANGES_REQUESTED instead when findings require changes. If unable to review, explain the blocker without an approval verdict.

@openhands-ai

openhands-ai Bot commented Oct 29, 2026

Copy link
Copy Markdown

Uh oh! There was an unexpected error starting the job :(

This branch was successfully deployed

1 active deployment
staging — 94aeb246 Deployed Oct 29, 2026 by mintlify[bot]
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.

1 participant