Changing tickets and repositories

Add tickets after a run, leave some out, and take a repository off a ticket so Claude never builds it there.

What you’ll learn

How to add tickets to a feature that already ran.
How to leave a ticket out of the next runs.
How to take a repository off a ticket, and put it back.

Features change

Product needs change after the first run. Livra lets you change a feature without starting over: Claude only sets up what is new, and runs skip what is already done.

Add tickets after a run

On the feature's page, click Add tickets (or More › Add or remove tickets).
The name, Jira project and epic stay as they are. You can pick another environment.
Tick the new tickets, or type their keys. Tickets already done in that environment are shown as done and can't be picked again.
Claude sets up only the new tickets. The saved setup of the others stays as it is.
Review, then save and check as usual.

The next Plan, Build and Document skip the tickets already done in that environment.

Example: after team-invites shipped to Development, product adds APP-110, "Show pending invitations in the mobile app". You click Add tickets, tick APP-110, and Claude sets up just that ticket. The next plan only covers the new work.

Leave tickets out

On the same page, untick a ticket to leave it out of the next runs. Its setup and earlier merge requests stay as they are, and the plan lists it under Skipped tickets. Tick it again later to bring it back.

Before the feature is saved, use Change tickets instead.

Take a repository off a ticket

Sometimes Claude proposes a repository a ticket shouldn't change. To remove it:

on the Set up page, under Tickets and where they’re built, click the × next to the repository; or
on step 4 of a new feature, click Remove next to it.

That ticket won't be built in that repository. The removal is kept on the ticket: later set-ups, Claude's proposals and runs never bring it back, and Claude is told which repositories were removed. On a saved setup, this makes a new setup version and asks for a new check.

Tip: removing a repository is more reliable than asking Claude to "ignore" it in chat, because the removal is remembered for every later run.

Put it back

On the Set up page, the ticket shows Removed: with the repository. Click Put back: the entry comes back as it was. If Claude never had its details, run Set up again so Claude finds them.

Tip: you can't change tickets or repositories while Claude is working on the feature. Wait for the step to finish, or stop it.

Check yourself

1. You add a ticket to a feature that already ran. What does Claude set up?

Only the new ticket. The saved setup of the others stays as it is.

2. Where does a ticket you unticked appear in the next plan?

Under Skipped tickets.

3. You removed a repository from a ticket. Will a later set-up propose it again?

No. The removal is kept on the ticket until you click Put back.