Deliver
Create Jira tickets
Turn a verified meeting into an epic and its stories.
Connecting Jira
There is nothing to find or install in Jira itself for this — no app to search for in a marketplace. Settings → Integrations → Connect next to Jira sends you straight to Atlassian's own consent screen; approve it as whichever Atlassian account can create issues in your target project, and you're back in CTX, connected.
From a meeting's bundle, CTX drafts a plan: one epic for the theme the meeting was about, and stories under it — each independently shippable, each built only from context items the meeting actually verified.
What each ticket includes
- A title and description written from the discussion, with acceptance criteria in Given/When/Then form.
- Constraints and open questions the meeting raised — an open question becomes a spike or is named as unresolved, never guessed at.
- The quotes every claim rests on, and a pointer to the full implementation prompt (the CTX panel on the issue, or the linked bundle).
- Labels and an optional story-point estimate, when the discussion gives CTX something to base one on.
Review before it reaches the board
- Dry run shows exactly what would be created or updated, and names any required field your Jira project demands that the meeting couldn't supply — answer it once, and CTX remembers it for that project.
- Approving a plan is a fact, not just a status: editing a ticket afterward withdraws the approval, so nobody's sign-off ever covers text they haven't seen.
- Pushing again after a change updates the existing issues rather than duplicating them.
Automating the push
Settings → Ticket automation has three modes: off, draft (a plan is always waiting for you to review), and auto. Auto only pushes without review once your workspace has approved and pushed a handful of plans by hand — autonomy here is earned, not just switched on. A ticket cap per meeting and a minimum-verified-items threshold guard against a three-minute standup turning into an epic; a playbook field lets you describe your team's own ticket-writing conventions in plain words.