Automate ticket pick-up with the Gearset Agent

Run a job on a schedule that finds tickets in Jira or Azure DevOps and starts Cam on each one.

Automated jobs are in pilot. To try them, contact us through the in-app chat.

What an automated job does

On each scheduled run, the job searches Jira or Azure DevOps for open tickets that match your filters and are unassigned or assigned to you. It starts a conversation with Cam for each one, up to the limit you set. It skips tickets that any job in your team has already started.

Cam writes a plan from the ticket's title and description, and waits for you to approve it. Each conversation has its own feature branch in the job's pipeline and developer sandbox. It appears in your conversation history and on your task board.

Before you start

You need access to the Gearset Agent, a Jira or Azure DevOps connection, and a pipeline with a developer sandbox. Your team must also be in the pilot.

Create a job

In the Gearset Agent sidebar, click Automate.
Click New automation job, or New job if you already have one.
On Job details, enter a Job name, choose the Pipeline, and choose a developer sandbox under Environment.
Click Continue. On Tickets, choose Jira or Azure DevOps under Issue tracker. Then set the Projects, Statuses, and Labels (tags in Azure DevOps) to match. Leave a filter empty to match anything.
Click Continue. On Schedule, choose Daily, Weekdays, or Weekly, and a time. The time zone is shown after the time. Then choose Tickets to start each run, from 1 to 5.
Click Create job.

The job appears on the Automate page, turned on, with the time of its next run.

Tip: To control which tickets Cam picks up, add a label such as agent to tickets when they're ready, and filter the job on that label.

Turn a job off or on

Use the switch next to Edit job. A job that's off shows Off and Next run not scheduled, and keeps its settings and run history. When you turn it back on, it runs at its next scheduled time.

If the job shows No schedule, the switch is unavailable.

Run a job now

Click Run now. This doesn't change the schedule, and works when the job is off. Run now is unavailable for 5 minutes after any run.

See what a job has done

Click a job to open its run history. Each run shows when it ran, its result, how many tickets it found, how many your team's jobs had already started, and how many it started. (maximum reached) means more tickets matched than the job could start in that run. Click a run to see the conversations it started.

Result	What it means
`Running`	The run is in progress.
`Finished`	The run completed. If it started nothing, see "A ticket wasn't picked up" below.
`Failed`	Something went wrong. The reason is shown under the result.
`Blocked`	The job can't run, and Gearset turned it off. See "My job was turned off" below.

Edit or delete a job

To edit a job, click Edit job, make your changes, and click Save changes. Saving doesn't turn a job back on.

To delete a job, open the ⋮ menu, click Delete job, and then click Delete. Conversations the job started aren't affected.

Limits

You can have up to 2 jobs. Each run starts up to 5 tickets, and leaves the rest for the next run. Jobs work with Jira and Azure DevOps, in developer sandboxes only.

Each run looks at the first 100 matching tickets. It does this before it removes tickets that are assigned to someone else or already started.

Troubleshooting

My job was turned off

Gearset turns a job off when it can't run, and shows a Blocked run with a message explaining why it was turned off:

A job keeps finding no tickets

If your Jira or Azure DevOps connection has expired or been removed, runs show Finished and No tickets found, not an error. Reconnect, and then click Run now. If the connection works, check the job's filters.

A ticket wasn't picked up

Check that the ticket matches every filter, is open, and is unassigned or assigned to you. A job matches the assignee against your Gearset display name or email. It also skips tickets that any job in your team has already started.

If the run shows (maximum reached), a later run will pick the ticket up. If your filters match more than 100 tickets, narrow them.

A run failed

The run history shows This run failed unexpectedly. Contact Gearset support if this keeps happening.

If a conversation fails to start, the run stops, and the remaining tickets aren't started. Conversations it already started stay open. Click Run now to try again. If it keeps failing, contact us through the in-app chat with the job name and the time of the run.