Your first feature

Create a feature in four short steps, from naming it to letting Claude find where each ticket will be built.

What you’ll learn

How to start a feature with New feature.
How to pick its Jira tickets.
How to read what Claude found during set-up, and correct it.
What happens when you save.

Before you start

Connect your Jira account first (see the lesson Connect your accounts). If Jira is not connected, the new feature page tells you so.

Nothing you do in these four steps changes any code. You can go Back at any time, and nothing is pushed anywhere until you approve the plan later.

Step 1 · About the feature

Click New feature at the top of the sidebar.

What should we call it? Use lowercase words joined by dashes, for example team-invites. The name is yours: a colleague can use the same name for their own feature.
What do you want to do? Choose Build new work: Claude writes the code for each ticket in your first environment (usually Development) and opens merge requests. The other choices, Move it to Staging and Release it to Production, carry finished work over from the environment before.
Jira project — pick it from the list, or type its key, for example APP. Then Continue.

Step 2 · Tickets

Choose the Epic and click Show my tickets to list your open tickets in it.
Tick the ones that belong to the feature. For team-invites, tick APP-101, APP-102 and APP-103.
A ticket that isn't in the list can be typed under Or type ticket keys, separated by commas or spaces.
Click Let Claude set it up.

Tickets whose Jira title carries an environment tag, such as [stage] or [prod], only load in that environment.

Step 3 · Claude sets it up

Claude now searches your repositories. This is read-only: nothing is changed. For each ticket it shows where it will be built, with how sure it is:

Sure — existing work or the ticket names it.
Likely — two clues agree.
Needs you — Claude asks instead of guessing.

When a ticket says Needs you, answer Claude's questions, then Save answers. The page also lists the Branches Claude will use.

If something looks wrong — say Claude picked the admin web app for a ticket that belongs to the accounts API — click Something wrong? Tell Claude and say it in your own words. Then Continue to review.

Tip: Claude asks rather than guesses. A question at this step costs you ten seconds; a wrong repository would cost a re-plan later.

Step 4 · Review and start

You see the repositories that will change, the Time to log at most, and the changes Claude suggested. If a repository shouldn't be built for a ticket, click Remove next to it.

When it looks right, click Save and check the setup. The feature is saved, appears in your Recents in the sidebar, and the Check phase starts.

Check yourself

1. Does creating a feature change any code?

No. Set-up is read-only, and nothing is pushed until you approve the plan.

2. What does "Needs you" next to a ticket mean?

Claude wasn't sure where the ticket belongs, so it asks you instead of guessing. Answer its questions and save.

3. A ticket's title in Jira starts with [prod]. Will it load when you build in Development?

No. Tagged tickets only load in their own environment.