Working without an issue tracker

What you’ll learn

• How a feature starts from a written description instead of tickets.
• What to write so Claude finds the right place.
• How to give Claude the design: Figma links or images.
• How to add another description later, and choose what each run works on.

When this applies

Some teams don't use an issue tracker. When your organisation works this way (an owner or maintainer chooses it in Settings › General › How features start), a new feature asks for a description of the change instead of a project, an epic and tickets. Features already started keep the way they began.

Describe the change

1. Click New feature, give it a name and pick the environment. There is no project to choose.
2. In Describe the change, write what should happen:
   • what users should see or be able to do;
   • the screens, endpoints, rules or repositories involved, if you know them;
   • how you'll know it works.
3. Give it a title (or let the first line be used) and a kind: new or changed behaviour, a bug fix, or technical work.
4. Click Let Claude set it up.

The description gets a key your organisation numbers itself — CR-1, CR-2… Branches, commits and merge requests use it like a ticket key. Claude reads the description, searches your code to find where it goes, and asks you when it isn't sure. Then you check the setup, approve the plan and build as usual. No time is logged.

Add the design

If the change shows on screen, give Claude its design under Designs:

• Figma links — one per line, the link of each frame (with its node-id), from Share › Copy link. Claude reads exact sizes, spacing and colours through your Figma connector.
• Images — mock-ups or screenshots: Add design images, drop them on the box, or paste a screenshot. PNG, JPEG, GIF or WebP, up to 5 MB each.

Claude uses them when it builds the screens, the same way as designs on a Jira ticket. The list of descriptions shows how many designs each one has.

Add another description later

1. On the feature's page, click Add a description.
2. Write the new change. The feature's earlier descriptions are listed above it, like tickets: their key, title, kind, and Read the description.
3. Claude works only with the ticked ones — by default just the new one. Tick an earlier one to work on it again; the ones already done in this environment can't be ticked.

Tips

• One change per description: it keeps plans and merge requests small.
• Name what you can see: a page, a button, an error message, an endpoint. Claude checks it against the code.