Jira, filed and moved from the conversation.
Ask what is in the sprint, file the bug the thread found, transition the issue, and Cedric proposes the change in Jira before it saves.
$50 in free credits when you sign up. No card needed.
- Jira is where engineering work is tracked and where everyone else stops reading.
- Ask in plain words or with an advanced query: the open bugs in this sprint, what is assigned to one person, what is blocked.
- The bug described in the thread becomes an issue with a summary, description, assignee, labels and priority, on your yes.
- Transitions, reassignments, comments, logged time and links to epics or subtasks are proposed first.
- Fields, workflows and permissions vary by site, so Cedric works within yours, and heavy searching can hit request limits.
What can a Jira AI agent do?
Reading comes first. Cedric searches for issues in Jira using keywords, filters or advanced queries and summarizes the results in plain words. It lists projects, boards, sprints and backlogs and which issues belong to each, looks up users and their assigned work, and checks an issue's history and its linked issues. A question like "what is still open in the sprint and who has more than three things" is answered in the thread, which is most of what AI project management means for a team that lives in Jira.
Then the writes. Cedric creates new issues, bugs, tasks or stories with a summary, description, assignee, labels and priority. It updates existing issues by editing fields, changing priority or reassigning them, and moves issues through the workflow, such as marking them in progress, blocked or done. It adds comments, logs time worked and attaches files. It creates and manages links between issues, subtasks and epics so dependencies show up where they belong. Every one of these changes real project data and comes back as a proposal first.
Jira sites differ. Available fields, workflows and permissions vary from one site to the next, so Cedric works with the transitions and fields your site actually has rather than assuming a default set. Heavy searching can hit request limits, so a very broad query is paged rather than pulled in one go.
The bug from the thread
Described once, filed once, linked to the epic.
Hannah Lindqvist9:14 AM
@Cedric file the export timeout we just discussed as a bug in PLAT, high priority, assign to Ravi, label backend, and link it to the Q3 reliability epic. Then move PLAT-418 to Done, the fix shipped.
CedricAPP9:15 AM
Proposed in PLAT: a new Bug, "CSV export times out above 50k rows", priority High, assignee Ravi Menon, label backend, description from the thread with the two example workspace ids, linked to PLAT-390 "Q3 reliability" as a child. And PLAT-418 "Retry on webhook 502" (In Review, assignee Ravi) transitions to Done. Your workflow allows that transition from In Review. Nothing saved yet.
Searched
Issues by keyword, filter or advanced query, summarized, with sprints, backlogs and each person's assigned work listed.
Filed
A bug, task or story with summary, description, assignee, labels and priority, from what the thread established, on your yes.
Transitioned
Moved through your workflow, reassigned, commented, time logged, and linked to an epic or subtask, proposed first.
Connect Jira in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect Jira from the dashboard
Open the Integrations page and sign in with Jira on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "what is still open in the current sprint?". You describe the outcome; Cedric picks the Jira actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold Jira into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
Code changes land in GitHub while the plan lives in Jira. Ask Cedric whether the sprint is on track and it reads the merged pull requests against the open issues and names the gap.
The bug is usually reported first in a support thread or a Gmail reply; Cedric can file it in Jira with the customer's words attached, and post the issue key back in Notion where the release notes are drafted.
Where the limits are
Jira is a catalog connection, not a built-in playbook. Cedric works from what the Jira connection can read and do; ask in plain words and it says what it can reach there, and what it cannot.
Fields, workflows and permissions vary by site. Cedric works with the transitions and fields your Jira site exposes to the connected user. If a transition is not allowed from an issue's current status, it says so instead of forcing it.
Heavy searching can hit request limits. A very broad query across many projects is paged, and a summary over the whole backlog takes longer than one over a sprint.
Cedric sees what the Jira connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes. Jira is one of the 3,200+ apps in Cedric's catalog: connect it once from the dashboard, on Jira's own sign-in screen, and ask in plain words. There is no built-in playbook for it, so Cedric works from what the connection can read and do, and tells you when something is out of reach.
No. Your automation rules keep running on every transition and edit. Cedric creates, edits and transitions issues the way a user with the right permissions would, and your rules react to those changes as usual.
Yes. It logs time worked against an issue, adds comments and attachments, and creates links between issues, subtasks and epics. Each of these is a write to project data, so it is proposed and saved on your yes.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Connect Jira in a minute.
Ask what is open in the sprint, then file the next bug from the thread that found it.
100K credits ($50) on sign up. No card needed.