Skip to content

Commit 6499b8e

Browse files
authored
Merge pull request #1972 from qodo-ai/hl/add_monday_integration_docs
Update fetching_ticket_context.md
2 parents 9bbed66 + 3980c0d commit 6499b8e

File tree

1 file changed

+46
-0
lines changed

1 file changed

+46
-0
lines changed

docs/docs/core-abilities/fetching_ticket_context.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ This integration enriches the review process by automatically surfacing relevant
1212
- [GitHub/Gitlab Issues](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#githubgitlab-issues-integration)
1313
- [Jira (💎)](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#jira-integration)
1414
- [Linear (💎)](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#linear-integration)
15+
- [Monday (💎)](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#monday-integration)
1516

1617
**Ticket data fetched:**
1718

@@ -451,3 +452,48 @@ Name your branch with the ticket ID as a prefix (e.g., `ABC-123-feature-descript
451452
```
452453

453454
Replace `[ORG_ID]` with your Linear organization identifier.
455+
456+
## Monday Integration 💎
457+
458+
### Monday App Authentication
459+
The recommended way to authenticate with Monday is to connect the Monday app through the Qodo Merge portal.
460+
461+
Installation steps:
462+
1. Go to the [Qodo Merge integrations page](https://app.qodo.ai/qodo-merge/integrations)
463+
2. Navigate to the **Integrations** tab
464+
3. Click on the **Monday** button to connect the Monday app
465+
4. Follow the authentication flow to authorize Qodo Merge to access your Monday workspace
466+
5. Once connected, Qodo Merge will be able to fetch Monday ticket context for your PRs
467+
468+
### Monday Ticket Context
469+
`Ticket Context and Ticket Compliance are supported for Monday items, but not yet available in the "PR to Ticket" feature.`
470+
471+
When Qodo Merge processes your PRs, it extracts the following information from Monday items:
472+
473+
* **Item ID and Name:** The unique identifier and title of the Monday item
474+
* **Item URL:** Direct link to the Monday item in your workspace
475+
* **Ticket Description:** All long text type columns and their values from the item
476+
* **Status and Labels:** Current status values and color-coded labels for quick context
477+
* **Sub-items:** Names, IDs, and descriptions of all related sub-items with hierarchical structure
478+
479+
### How Monday Items are Detected
480+
Qodo Merge automatically detects Monday items from:
481+
482+
* PR Descriptions: Full Monday URLs like https://workspace.monday.com/boards/123/pulses/456
483+
* Branch Names: Item IDs in branch names (6-12 digit patterns) - requires `monday_base_url` configuration
484+
485+
### Configuration Setup (Optional)
486+
If you want to extract Monday item references from branch names or use standalone item IDs, you need to set the `monday_base_url` in your configuration file:
487+
488+
To support Monday ticket referencing from branch names, item IDs (6-12 digits) should be part of the branch names and you need to configure `monday_base_url`:
489+
```toml
490+
[monday]
491+
monday_base_url = "https://your_monday_workspace.monday.com"
492+
```
493+
494+
Examples of supported branch name patterns:
495+
496+
* `feature/123456789` → extracts item ID 123456789
497+
* `bugfix/456789012-login-fix` → extracts item ID 456789012
498+
* `123456789` → extracts item ID 123456789
499+
* `456789012-login-fix` → extracts item ID 456789012

0 commit comments

Comments
 (0)