Start from a requirement to complete the backlog

Paste an email, meeting notes or a specification: AI matches it against the existing backlog, completes the right epics and flags what is already covered.

Plan

All plans

Required permission

Tickets › CreateDefault: Product Owner, Scrum Master, Business Analyst, plus the project owner and admins.

Required permission

Epics › CreateDefault: Product Owner, Scrum Master, Business Analyst, plus the project owner and admins.

#When to use it

The Launchpad creates a backlog from scratch. Start from a requirement is for a project already under way: a client request, the outcome of a steering committee, an amendment to the specification. AI does not recreate what exists: it attaches the new tickets to the epics concerned.

#Launch it

Three entry points:

• the Start from a requirement line at the top of the ticket, epic and Super Epic creation windows;
• the Add a requirement to the backlog action in global search (Ctrl+F);
• from an epic's or Super Epic's page: the requirement is then targeted at it. Widen to the whole backlog removes that targeting.

#The steps

1. Paste the text of the requirement, and/or drop documents.
2. Analyse the requirement. The maximum credit cost is shown before you start.
3. Check the proposal:
   • for each part of the requirement, the epic it attaches to (existing, or New epic), which you can change;
   • Already covered by your backlog: what already exists;
   • Outside the backlog: what is not work to plan.
4. Tickets close to an existing ticket are unticked by default: check them. Untick what you do not want.
5. Add to backlog.

New epics can be grouped under a new Super Epic.

The cost of each step is in AI credits.