Compare commits

...

15 Commits

Author SHA1 Message Date
Rohit Malhotra
c8f2bb2a7d Merge branch 'main' into enable-jira 2025-10-01 15:00:49 -04:00
rohitvinodmalhotra@gmail.com
d20d39c83a Update jira-integration.mdx 2025-10-01 14:47:45 -04:00
rohitvinodmalhotra@gmail.com
b21701e1ad revert debug prints 2025-10-01 14:47:22 -04:00
rohitvinodmalhotra@gmail.com
116f0c0514 make it a note 2025-10-01 14:39:09 -04:00
rohitvinodmalhotra@gmail.com
0e7230451e move note 2025-10-01 14:37:00 -04:00
rohitvinodmalhotra@gmail.com
2c114ccea4 move note 2025-10-01 14:36:31 -04:00
rohitvinodmalhotra@gmail.com
9363aec4e0 add regular user setup 2025-10-01 14:33:36 -04:00
rohitvinodmalhotra@gmail.com
7b7761c588 add accordion 2025-10-01 14:31:59 -04:00
rohitvinodmalhotra@gmail.com
71fbe17ec1 rm coming soon 2025-10-01 14:27:47 -04:00
rohitvinodmalhotra@gmail.com
4bd14c9dfc Update jira.py 2025-10-01 12:51:37 -04:00
openhands
641a9e78bd Add comprehensive debug logging to JIRA callback function
- Add debug prints at callback start to verify function is called
- Add error handling and logging around Redis session retrieval
- Add debug logging for token exchange with JIRA
- Add debug logging for JIRA resources fetch
- Add debug logging for JIRA user info retrieval
- Wrap API calls in try-catch blocks for better error visibility

This will help identify where the callback is failing and why it's
redirecting to GitHub OAuth instead of completing the JIRA flow.
2025-10-01 16:20:37 +00:00
rohitvinodmalhotra@gmail.com
8e9e5dd11a Update jira.py 2025-10-01 10:10:18 -04:00
rohitvinodmalhotra@gmail.com
9323267898 update docs 2025-10-01 09:28:26 -04:00
rohitvinodmalhotra@gmail.com
23a98b452b debug logs 2025-10-01 09:27:39 -04:00
rohitvinodmalhotra@gmail.com
7f530c33ae update docs 2025-10-01 09:26:01 -04:00
2 changed files with 35 additions and 13 deletions

View File

@@ -1,10 +1,21 @@
---
title: Jira Cloud Integration (Coming soon...)
title: Jira Cloud Integration
description: Complete guide for setting up Jira Cloud integration with OpenHands Cloud, including service account creation, API token generation, webhook configuration, and workspace integration setup.
---
# Jira Cloud Integration
<Note>
The workspace name is the host part of your Jira Cloud URL.
For example, if your Jira URL is `https://all-hands.atlassian.net/browse/OH-55`,
then your **workspace name** is **all-hands.atlassian.net**.
You will need this when connecting to Jira from OpenHands Cloud.
</Note>
<Accordion title="🛠️ Setup Instructions (Admin Only)">
## Platform Configuration
### Step 1: Create Service Account
@@ -26,7 +37,8 @@ description: Complete guide for setting up Jira Cloud integration with OpenHands
1. **Access Service Account Configuration**
- Locate the created service account from above step and click on it
- Click **Create API token**
- Click **Create Credentials**
- Select **API Token**
- Set the expiry to 365 days (maximum allowed value)
- Click **Next**
- In **Select token scopes** screen, filter by following values
@@ -75,21 +87,13 @@ description: Complete guide for setting up Jira Cloud integration with OpenHands
2. **Configure Workspace**
- Click **Configure** button
- Enter your workspace name and click **Connect**
- **Important:** Make sure you enter the full workspace name, eg: **yourcompany.atlassian.net**
- **Important:** Make sure you enter the full workspace name, e.g. **yourcompany.atlassian.net**
- If no integration exists, you'll be prompted to enter additional credentials required for the workspace integration:
- **Webhook Secret**: The webhook secret from Step 3 above
- **Service Account Email**: The service account email from Step 1 above
- **Service Account API Key**: The API token from Step 2 above
- Ensure **Active** toggle is enabled
<Note>
Workspace name is the host name when accessing a resource in Jira Cloud.
Eg: https://all-hands.atlassian.net/browse/OH-55
Here the workspace name is **all-hands**.
</Note>
3. **Complete OAuth Flow**
- You'll be redirected to Jira Cloud to complete OAuth verification
- Grant the necessary permissions to verify your workspace access.
@@ -109,6 +113,24 @@ Here the workspace name is **all-hands**.
- This will deactivate your workspace link
- **Important:** If the original user who configured the integration chooses to unlink their integration, any users currently linked to that workspace integration will also be unlinked, and the workspace integration will be deactivated. The integration can only be reactivated by the original user.
</Accordion>
<Accordion title="👥 Setup Instructions (Regular Users)">
If your **admin has already completed the Jira Cloud integration** for your company, you only need to:
1. **Log in to OpenHands Cloud**
- Go to [OpenHands Cloud](https://app.all-hands.dev/)
- Sign in with your Git provider (GitHub, GitLab, or BitBucket)
2. **Connect to Your Company Jira Workspace**
- Go to **Settings** > **Integrations**
- Locate the **Jira Cloud** section
- Click **Configure**
- Enter your companys Jira workspace URL (e.g., `yourcompany.atlassian.net`)
- Complete the OAuth flow when prompted
</Accordion>
### Screenshots
<AccordionGroup>

View File

@@ -1,5 +1,5 @@
---
title: Project Management Tool Integrations (Coming soon...)
title: Project Management Tool Integrations
description: Overview of OpenHands Cloud integrations with project management platforms including Jira Cloud, Jira Data Center, and Linear. Learn about setup requirements, usage methods, and troubleshooting.
---
@@ -18,7 +18,7 @@ Integration requires two levels of setup:
2. **Workspace Integration** - Self-service configuration through the OpenHands Cloud UI to link your OpenHands account to the target workspace
### Platform-Specific Setup Guides:
- [Jira Cloud Integration (Coming soon...)](./jira-integration.md)
- [Jira Cloud Integration](./jira-integration.md)
- [Jira Data Center Integration (Coming soon...)](./jira-dc-integration.md)
- [Linear Integration (Coming soon...)](./linear-integration.md)