Skip to lesson
Exit
Start cloud agents from work systems1 / 2

1 min lesson

Route WEB-184 from Jira to a PR

Route WEB-184 from Jira to acme/web-app, then review the PR that Jira returns.

Step 1 of 2

Connect Jira to the intended Cursor team and confirm that the source control provider can reach acme/web-app. Check usage-based pricing, privacy and whether runs use a service account or individual authentication. Open WEB-184. Because the issue names both web and API work, add @Cursor with repo=acme/web-app and branch=release, then ask for the search fix and its tests. Open the Cloud Agent as soon as it starts. Compare its source item, repository, branch and task with the Jira comment. Follow progress in Jira and use Rovo chat for any follow-up to the active run. When Jira posts the completion summary, open its PR link. Verify the target branch, diff and test results before accepting the handoff.

Learn more

Full explanation

Jira work item, explicit repository and branch, PR handoff

Route one Jira issue to the right repository
Jira work item, explicit repository and branch, PR handoff
SayWEB-184 describes intermittent empty search results. It mentions the web app and API, so an automatic route could choose the wrong repository.
DoIn Cursor Cloud Agent settings, confirm that Jira is connected, the source control provider can access acme/web-app, usage-based pricing is enabled and privacy is set. Check whether the team uses service account or individual authentication.
SeeThe intended identity can run against acme/web-app, and its defaults are visible before launch.
DoOpen WEB-184. Add this comment: @Cursor repo=acme/web-app branch=release reproduce the empty search result, fix its cause, and update the search tests.
SeeJira starts a Cloud Agent from the work item. The task includes its title, description, comments, repository and base branch.
DoOpen the run as soon as it starts. Confirm WEB-184, acme/web-app, release and the requested test update. If the route is wrong, do not use that run's changes. Correct the route first.
SeeThe source item and code boundary agree before the run becomes a handoff.
DoFollow the status in Jira. If the agent needs more detail, open Rovo chat from WEB-184 and continue the existing conversation.
SeeThe follow-up stays with the active agent and Jira keeps the progress beside the work item.
DoWhen the run completes, open the PR from Jira. Verify that it targets release, the diff fixes the empty result and the search tests pass. Keep the PR link and completion summary on WEB-184.
SeeA reviewer can move from the original work item to the exact PR and check the result without reconstructing the task.
Learn more

Optional practice

Test yourself on Route WEB-184 from Jira to a PR

QWhich result proves WEB-184 reached the right code and came back with a checked PR?