Jira & Linear Tickets
The primary "wedge" feature of Plan AI is automating the most tedious part of technical project management: writing and scoping tickets.
Rather than a TPM spending hours listening to a meeting recording and manually typing out acceptance criteria, Plan AI generates perfectly scoped tickets instantly.
How it Works
When you finish a meeting, the transcript is automatically processed. From the Web Dashboard, you can navigate to the Tasks tab of your meeting.
By default, Plan AI will attempt to extract:
- Bugs mentioned during the call.
- Feature Requests or new requirements.
- Action Items assigned to specific people.
For each item, the AI generates a title, a description, and a set of technical acceptance criteria.
Pushing to Issue Trackers
Once the tickets are generated, you can push them directly to your external issue tracker.
- Review the generated ticket in the Plan AI dashboard.
- Click the Push icon next to the ticket.
- Select your destination (e.g., Jira or Linear).
- The ticket will be created instantly in your backlog with the correct formatting.
(Note: Linear and Jira integrations must be configured by an Admin in the Workspace Settings before you can push tickets).
Using Contexts for Perfect Scoping
Generic AI often generates terrible Jira tickets because it lacks understanding of your specific codebase. A generic ticket might say "Add login button", which is useless to a developer.
Plan AI solves this using Contexts.
Before generating tickets, you can attach a "Context" to the meeting. A Context is a collection of:
- Architecture documentation
- API schemas
- Previous meeting decisions
When the AI generates the ticket, it cross-references the meeting audio with your attached Context. Instead of "Add login button", it will generate: "Implement SSO login button in SidebarLayout.tsx using the existing AuthContext provider, ensuring the Firebase token is passed to the POST /api/auth endpoint."
This turns a 5-minute manual task into a 1-second automated task.