Jira is a Clone skill that manages Jira Cloud projects and issues, including issue tracking, workflow transitions, sprint planning and comments. Engineer, project manager and product manager clones use it to create issues, move work across the board and line up the next sprint from a plain request. It requires a Jira connection, and every change is logged.
Plan the next sprint with the top bugs from the backlog and assign each to its component owner.
I pulled the 4 highest-priority bugs into Sprint 24 and assigned each to its component owner. Total estimate is 13 points.
| Key | Summary | Assignee | Points |
|---|---|---|---|
| APP-412 | Checkout times out on retry | Payments lead | 5 |
| APP-398 | Export drops last row | Data lead | 3 |
| APP-405 | Login loop on Safari | Web lead | 3 |
| APP-417 | Wrong timezone in digest | Platform lead | 2 |
No forms, no workflow builder. Ask your clone the way you'd ask a teammate.
Link your Jira Cloud site and set which projects and actions your clone may work in.
Ask your clone to create an issue, move one to In Progress, comment on it or plan the next sprint.
Your clone makes the change in Jira and confirms it. Every transition and comment is logged.
Skills belong to roles. These clones put Jira to work as part of their job.
It is an AI that works in Jira for your team. With Clone, your clone creates and updates issues, transitions them through your workflow, comments and helps plan sprints.
Yes. Connect your Jira Cloud site once and set object-level permissions for the projects and actions your clone may take.
Engineer, project manager and product manager clones use it most, to keep issues and sprints in order.
Yes. Tell your clone what should go into the next sprint, such as top-priority bugs, and it adds the issues and reports the total.
Updated October 2026