Jira AI Agent that automates sprints, overdue issues and issue moves

Name: Jira AI Agent that automates sprints, overdue issues and issue moves
Availability: InStock
Author: Katteb

Work & productivity atlassian.net

A ready-made Katteb agent for teams that use Jira on atlassian.net to run Scrum and track work. It reads the current sprint, finds overdue issues and assignees, and can move the exact issues you name into the next sprint with a comment.

Build a Jira agent All agents

What a Jira agent does

The jobs people usually do here by hand. Tap one in the app and it becomes a plan.

Summarise the current sprint: done, in progress and blocked.
List issues past their due date and who they belong to.
Move the issues I name to the next sprint with a comment.

Anything else you would do in this site by hand can be described in your own words: the planner turns it into a plan you approve before it runs.

What people use it for

Summarise the current sprint

Get a clear list of issues in Done, In Progress and Blocked with counts and a screenshot of the board. Useful for daily stand-ups and sprint reviews so the team knows what finished and what needs help.

List overdue issues and owners

Produce a dated list of issues past their due date, plus the assignee and project. Use it to reassign work, update stakeholders, or populate a calendar view that shows upcoming risk.

Move named issues to the next sprint with a comment

Tell the agent which issue keys to move; it will open them in your browser, add a comment you approve, and move each issue to the next sprint or backlog according to Jira rules and your permissions. This preserves history and sprint tracking.

Why it is worth it

Saves time on repetitive sprint reporting and manual issue moves
Provides a dated screenshot report suitable for stand-up notes
Keeps assignee and due-date visibility before planning
Operates through your browser so no API tokens are stored by Katteb

Questions people ask

What permissions does the Jira agent need?

The agent uses your browser session, so it needs the same Jira permissions you have. To move or schedule issues you must have Edit Issues and Schedule Issues on the relevant projects; otherwise moves go to the backlog.

Is automated activity inside our Jira account detectable or risky?

The agent acts like a user in your private browser and may appear in audit logs or recent activity. That carries the same risk as any automated or repetitive user activity; Katteb does not claim it is undetectable or risk-free. Follow your org policies. (Agent stops if a page requests a password.)

How are runs scheduled and billed?

You sign into the private Katteb browser once, approve a run plan in English or Arabic, then run now or schedule daily/weekly. Each run charges only for what it used and the report arrives in chat with a screenshot. Katteb bundles agents in monthly plans but charges per-run usage separately.