Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Cursor couldn't determine which repository to use for this Jira request. Add a routing rule that nam

Cursor couldn't determine which repository to use for this Jira request. Add a routing rule that nam

Ben Katz
May 26, 2026

I've setup the Jira / Cursor integration. 

I've set a default repo in our Cursor cloud agent settings.

Yet, when I try to ask Cursor to do something from Jira, it says:

"Cursor couldn't determine which repository to use for this Jira request. Add a routing rule that names a repository for this kind of work, or set a default repository in your Cloud Agents settings."

2 answers

1 vote
Ben Katz
May 26, 2026

If in the message to the agent, I put `[repo=owner/repo-name]` then it responds with:

 

Cursor cannot use [OUR REPO NAME] for this Jira request because it is not in the Cloud Agents routing context. No repositories are configured for Jira routing yet.

0 votes
Matheus Oliveira
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 27, 2026

I am having the exact same issue in my organization trying to setup cursor agent in JIRA.
I have trying setting the routing rules and default repo, and didn't work.
Any solution?

Ben Katz
May 27, 2026

So the only way I could get it to work, is to go the Cursor Jira integration settings at this url: https://cursor.com/dashboard/integrations?view=jira-management

Then, enable the switch that says "Require individual authentication"

Of course, this does mean that each Jira user will need to link their own cursor account to their own Jira account. But at least this got it to work. 

Screenshot 2026-05-27 113220.png

Like Matheus Oliveira likes this
Matheus Oliveira
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 29, 2026

I'm seeing your response just now, but I ended up finding the exact same solution.
Thank you so much, @Ben Katz

Now we're seeing another issue: the issueKey that is being sent to Cursor is wrong, so we end up with the wrong links and information on the PRs. Have you had this issue?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events