Skip to main content

How to pick your first ticket for Cam

What makes a good first ticket for Cam, the Gearset Agent, plus a template you can copy into Jira or Azure DevOps.

Written by Hazel Izzett

Your tickets are probably good enough for Cam already. What matters more is picking the right size to start with.

Nothing ships without your approval. You see Cam’s questions and its plan before anything is built, and every change goes through your pipeline as a pull request.

This guide covers what to pick, what Cam can’t do yet, and a template you can copy into Jira or Azure DevOps.
​

What makes a good first ticket

Pick a real ticket from your backlog rather than a made-up test, so you see how Cam handles your own org. The best first tickets are the kind of work you’d hand a new hire in their first week. For example:

  • Add a field to an object and its page layout

  • Add a validation rule

  • Update a permission set

  • Make a small change to an existing flow

  • Fix a bug you can reproduce

Choose something that would take you a few hours by hand and touches a handful of components. That gives you a pull request you can review in one sitting before you hand Cam anything bigger.

What Cam can’t do yet

Leave these out of your first tickets:

  • CPQ and Revenue Cloud changes, and other changes that live in configuration data rather than metadata

  • OmniStudio configuration

  • Agentforce agents

If most of your team’s changes fall into these areas, get in touch with us through the in-app chat or speak to your account manager before you start.

What Cam needs from a ticket

“How good does a ticket need to be?” is one of the first things teams ask. Cam needs less than you might think. It reads your org and repo before it designs anything, so it already knows your objects, fields, flows and automations. If something’s missing from the ticket, it asks. You answer by picking one of its suggested options or replying in your own words.

So a one-line ticket is fine. But if you already know some extra detail, put it in. If you know which permission sets need access to a new field, say so.

What helps most:

  • The outcome you want, in a sentence

  • Anything you’ve already decided, like field types, names or who gets access

  • Anything Cam should leave alone

Leave the technical steps and metadata details to Cam.

Ticket template

Copy this into Jira or Azure DevOps. Only the first line is needed. Fill in the rest if you know it.

Summary: [What should change, in one sentence]
Why: [Who asked for it, and the problem it solves]
Done when: [How you’ll check it, e.g. “Reps can edit the field, finance can’t”]
Already decided: [Field types, names, picklist values, who gets access]
Leave alone: [Anything Cam shouldn’t change]
Related: [Names of fields, flows or objects this touches, if you know them]

First ticket checklist

  • It’s a real ticket from your backlog, not a made-up test

  • It would take you a few hours by hand, and touches a handful of components

  • It isn’t CPQ, Revenue Cloud, OmniStudio or Agentforce work

  • You’ve added anything you already know, like access, names, or what to leave alone

  • You’ve noted roughly how long it would take you by hand, so you can compare

Run your first ticket

  1. Open Cam from your dev sandbox in the pipeline, or from Gearset Agent in the sidebar.

  2. Pick your ticket from Jira or Azure DevOps, or describe the change in the chat.

  3. Answer Cam’s questions.

  4. Read the plan. Ask for changes if anything’s off, then approve it.

  5. Review what Cam built in the comparison view. If you want to test it first, deploy it to a sandbox. Then raise a pull request and promote it through your pipeline like any other change.

Want the plan on the Jira ticket too? Cam doesn’t post back to Jira by default. With the Jira connection turned on, ask it to add the plan to the ticket’s comments. To make that the default for your team, add it to your AGENTS.md file.

Build up from there

Once your first ticket has shipped, take on more, one step at a time:

  1. One or two more tickets like your first.

  2. A few tickets at once. Cam works on them side by side, and you review each one as it’s ready.

  3. The tickets that eat your team’s time: tech debt, changes across several objects, flows and Apex.

Hold off on bulk work, like a change that touches hundreds of components at once, until you’ve seen how Cam works with your org. Big changes are harder for you to review, and if something looks wrong, it’s harder to tell which change caused it.

Further help

For a full walkthrough, see How to deliver your first change with Cam and Working with the Gearset Agent. If you’d like a hand with your first ticket, get in touch with us through the in-app chat or speak to your account manager.

Did this answer your question?