Where does the bug appear (feature/product)?
Somewhere else…
Describe the Bug
Cannot assign Jira tickets to Cursor App with Gitlab cloud hosted repository.
Steps to Reproduce
Gitlab connection for Cloud Agents instead of Github. Jira app installed. Assign a Jira ticket to the Cursor App.
Expected Behavior
Should initiate Cloud Agent with Gitlab repository.
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
Jira App Integration
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
Hi! Thanks for the detailed report and screenshots.
This is a known limitation with the Jira integration and GitLab.com (cloud) repos specifically. When the integration runs Cloud Agents under a shared service account, it resolves the repository in a way that defaults to GitHub, which is why you’re seeing the “Cursor GitHub App is not installed” error for your GitLab repo. Improving GitLab.com support for this flow is something we’re actively working on.
The most reliable way to unblock today is to switch the integration to user-level (individual) authentication:
- A team admin enables individual authentication in the Jira integration settings in the Cursor dashboard.
- Each user connects their account the first time they trigger an agent from Jira.
- In this mode the agent resolves repositories from the user’s own connected GitLab, which avoids the GitHub default.
Setup details: Jira integration docs
You can also try pinning the repo explicitly in the Jira comment with the full URL: @Cursor repo=https://gitlab.com/everlywell/apps/www <your instructions>
If neither unblocks you, reply here and we’ll take a closer look.
No difference with personal authentication enabled or with specifying the repo.
A couple of adjustments should help:
-
Use gitlab.com without the www. — the integration only recognizes the canonical host, so www.gitlab.com won’t be picked up as GitLab.
-
The repo= needs to go in the Jira comment that triggers Cursor (the one where you @-mention/assign Cursor), not the chat box afterward. So the trigger comment should be:
@Cursor repo=https://gitlab.com/everlywell/apps/www <your instructions>
If it still resolves to GitHub after that, the most reliable path is the individual (user-level) authentication option from my last reply - in that mode the agent resolves repositories from your own connected GitLab and skips the GitHub default entirely. Setup: Jira integration docs
Same behavior. Same if I have individual authentication enabled as well.
Interesting, thanks for testing both. It’s a limitation in how the Jira integration currently resolves GitLab.com repos: when the repo is passed inline with repo=, the integration drops the gitlab.com host and falls back to GitHub, which is why you keep seeing the “GitHub App is not installed” error for everlywell/apps/www.
The more reliable path is to set the repo as a default repository (or a routing rule) in your Cloud Agents settings rather than passing it inline - that path keeps the full GitLab URL and avoids the GitHub fallback:
- In the Cursor Dashboard, open Cloud Agents settings - under Team Settings if you’re on service-account auth, or My Settings if you’re on individual auth (Jira integration docs).
- Set the Default repository to the full URL:
https://gitlab.com/everlywell/apps/www (or add it as a Routing Rule for the relevant keyword).
- Trigger the agent from Jira again - you can drop the
repo= line and let it use the default.
I’m also notifying the team about this and will get back to you once I hear back.
