Rovo agent and AI tools
Advanced Export comes with a Rovo agent. Ask it in plain language to set up, run and check your reports, and it does the work with the same exports, schedules and permissions as the Advanced Export dashboard:
I'd like to report all items past due date. Schedule the report weekly as an attachment to email to me.
Email a teammate a CSV of the summaries and assignees in the current sprint.
Which of my scheduled reports failed in the last 30 days?
Anything the agent creates appears in the dashboard, and you can change it there.
The same tools are also available to your own Rovo Studio agents and, in early access, to other AI assistants that support the Model Context Protocol (MCP). See Other AI assistants.
Finding the agent
The agent is called Advanced Export. It is installed together with the app, so there is nothing to set up.
- Open Rovo chat in Jira.
- Open the agent list (Browse agents) and search for Advanced Export.
- Choose Chat to agent, or pick one of its suggested prompts.
The suggested prompts are a good place to start:
- Which of my scheduled reports failed in the last 30 days?
- Email a teammate a CSV of the summaries and assignees in the current sprint
- Upload a weekly report of work items closed in the last 7 days to SFTP
- Show me the first 10 rows of one of my reports
- Set up a monthly report of time spent in each status for a project
Rovo must be available on your Jira site. If you can't see the agent, check with your Jira admin that Rovo is turned on and that your Advanced Export installation is up to date.
What you can do with the agent
Find things
- Your exports, the public exports on your site, and their schedules.
- Jira fields (including custom fields), people, boards, sprints and saved filters, so the agent can build a report without you looking up any ids.
- Your SFTP servers and report templates.
Show data
- A live preview of any export: the data as it is now, as you can see it in Jira.
- The rows of a delivered file: what a scheduled run actually sent, while its download link is still valid.
- Change history: with history mode on, a report has one row per change, with how long each state lasted, so the agent can show things like time spent in each status.
See Where the data comes from for the difference.
Set things up
- Save a new export, or change one you own: which work items it includes (JQL, a saved filter, or a board and sprint), its fields, and whether it includes change history. New exports are private unless you ask for them to be public.
- Schedule an export as CSV, Excel (XLSX) or JSON, delivered by email, as a download link, to your SFTP server, or for the Advanced Export API, on any recurrence ("every Monday at 8", "on the first day of each month").
- Change a schedule's timing, format, recipients or destination.
- Pause and resume schedules.
Deliver now
- Run a schedule once, straight away.
- Send an export once, with no schedule at all (a one-off delivery).
Check runs
- Which runs succeeded or failed, when, and why, across all the schedules you can see.
- The details of one run: the error or warning, the number of rows, the file size, and whether a stored copy of the file can still be read.
What the agent cannot do
- Delete exports or schedules. To stop a report, ask the agent to pause it, or delete it in the dashboard.
- Add SFTP servers, webhooks or API keys, or read their credentials. Set those up in the dashboard.
- Create or change webhook deliveries.
- Anything you could not do yourself in the dashboard.
An example conversation
Ask for what you want. The agent looks up the fields it needs, checks the JQL and previews the data before it saves anything:
It then shows you what it found and what it is going to set up: the query, the format, the recipients and when it will run. Nothing has been saved yet.
When you agree, Rovo asks you to confirm each change. See You confirm every change.
Where the data comes from
When you ask the agent to show you a report, there are two different things it can show. The agent always tells you which one you are looking at.
| Live preview | Delivered file | |
|---|---|---|
| What it is | The export run now, by the agent | The file a scheduled run produced and delivered |
| When it is available | Always | Only for reports delivered as a download link, through the API, or as a webhook file, and only until the download link expires (at most 7 days) |
| Whose permissions | Yours: it shows only work items you can see in Jira | The permissions the schedule ran with: its owner's, or the app's if the schedule generates with add-on permissions |
| Size | A limited number of work items. The agent tells you when it is showing only part of the data | The whole file, read a page at a time |
Reports delivered by email or SFTP are not stored by Advanced Export, so for those the agent can show a live preview, but not the file that was sent. This is the same as the dashboard: see Your data on our servers.
Safety and permissions
An agent reads work item content, and anyone who can edit or comment on a work item can write text that tries to steer it. So Advanced Export does not rely on the agent behaving well. The rules below are enforced by Advanced Export itself, whatever the agent is told, and they apply equally to Rovo Studio agents and other AI assistants.
The agent acts as you
- Your identity comes from Atlassian, not from the conversation. Rovo tells Advanced Export who is asking. Nothing typed into the chat, or written in a work item, can make the agent act as someone else or on another site.
- It reads Jira with your permissions. Previews, field and user lookups and JQL checks run as you, so they show only what you can see in Jira. They never borrow the permissions of the export's owner or of the app.
- It sees what you see in the dashboard. Your own exports and the public exports on your site, and their schedules and runs.
- It changes only what you own. You can save new exports. Only the owner of an export can change it, or create, change, pause or run its schedule.
- Files generated with add-on permissions stay restricted. A delivered file from a schedule that generates with add-on permissions may contain more than any one person can see, so only the export's owner and Jira admins can read it through the agent.
- No new permissions. The agent uses the access the app already has. Installing or updating it did not ask your admin to approve anything new.
Reports go only where your site already sends them
- Recipients are people on your Jira site. The agent finds them by name and asks you to choose when two people match. Their email addresses are looked up by the app and are never shown to the agent.
- Email addresses outside Jira are off by default. A Jira admin can allow them in Settings (Jira settings → Apps → Advanced Export Settings → Scheduled Reports, under AI agents), with Allow AI agents to send reports to email addresses outside Jira. Leave it off unless you need it.
- SFTP only to your own servers. The agent can deliver only to SFTP servers you have already set up yourself in the dashboard. It cannot add a server or read its credentials.
- No webhooks. The agent cannot create or change a webhook delivery.
You confirm every change
Rovo asks you before the agent creates or changes an export or schedule, pauses or resumes a schedule, or runs or sends a report. Each change is listed with its details, and nothing happens until you choose Confirm selected. Cancel stops it.
Before it asks, the agent also tells you in plain words who will receive the report and when it will run. After it saves a schedule, it shows the next run times so you can check them.
Rovo agents started by a Jira automation rule cannot make changes at all, because there is nobody to confirm them. They can still find and show data.
Scheduling restrictions apply to the agent
If a Jira admin has restricted scheduling to some groups and project roles, the agent is restricted in exactly the same way as the dashboard. If you are not allowed to schedule, it cannot create, change, pause or run schedules for you, or send an export, and it tells you:
A Jira admin has restricted scheduling on this site to some groups and roles, and you are not in them. You can still run exports in the dashboard.
You can still save exports with the agent, preview them, and export in the browser.
Everything is recorded
Every change made through the agent is recorded with who asked for it and when.
Rate limits
To keep an agent that has gone wrong from flooding inboxes or your Jira site, each person can make, per site and per hour:
| Limit | |
|---|---|
| Runs and sends (run a schedule now, send an export now) | 20 an hour |
| Changes (create or change an export or schedule, pause or resume) | 60 an hour |
Attempts count even when they are refused. When you reach a limit the agent tells you when you can try again. Finding and previewing data are not limited this way.
Licence
Running a schedule now or sending an export now follows the same licence rules as scheduled reports.
One-off deliveries
An export has one schedule: the one the dashboard shows and edits. If you ask the agent to schedule an export that already has one, it offers to change that schedule instead. It cannot add a second one.
When the agent sends an export once ("send this to Jane now"), Advanced Export records it as a one-off delivery of that export. It never repeats, and it cannot be switched on as a schedule. It does not replace the export's schedule in the dashboard, and its run is not shown in the export's execution log. Ask the agent whether it succeeded, when it ran, and about any error. To send it again, ask the agent.
Tool catalogue
These are the tools the agent uses. You will see their names in Rovo while the agent works ("Invoking tool: Find fields"). The same tools are available to your own Rovo Studio agents and to other AI assistants.
Tools that change something are marked Confirm: Rovo asks you before each one runs.
Lookups
| Tool | What it does |
|---|---|
| Find fields | Finds Jira fields by name, including custom fields and Advanced Export's change history fields, and returns their ids |
| Find users | Finds active people on your site by name. Never returns email addresses |
| Find boards | Finds boards by name, with their type and project |
| Find sprints | Finds sprints by name or board, with their state and dates |
| Find filters | Finds saved filters you can see, with their JQL |
| Validate JQL | Checks a JQL query and returns Jira's errors, or roughly how many work items it matches |
| List SFTP servers | Lists the SFTP servers you can use: name and host. Never credentials |
| List templates | Lists the report templates on your site you can see |
Exports
| Tool | What it does | |
|---|---|---|
| List exports | Lists the exports you can see | |
| Get export | Shows one export's definition: which work items, fields, history mode, options and schedule | |
| Preview export | Runs a saved export, or an unsaved query, as you and returns the first rows: a live preview | |
| Create export | Saves a new export. Private unless you ask for it to be public | Confirm |
| Update export | Changes an export you own | Confirm |
Schedules
| Tool | What it does | |
|---|---|---|
| List schedules | Lists the schedules you can see, with their latest run, and marks one-off deliveries | |
| Create schedule | Schedules an export you own: recurrence, format, delivery and recipients. Returns the next run times | Confirm |
| Update schedule | Changes a schedule's timing, format, recipients or destination | Confirm |
| Pause or resume schedule | Pauses a schedule, or resumes a paused one | Confirm |
| Run schedule now | Runs a schedule once, straight away | Confirm |
| Send export now | Delivers an export once, with no schedule | Confirm |
Runs
| Tool | What it does |
|---|---|
| Get execution status | A schedule's recent runs, and the progress of one that is running now |
| List executions | Runs across all the schedules you can see, filtered by status, date, schedule or export |
| Get execution details | One run: its error or warning, rows, size, whose permissions it ran with, and whether its file can still be read |
| Read execution result | Reads the rows of a delivered file, a page at a time |
Using the tools in your own agents
Rovo Studio
You can build your own agent in Rovo Studio and give it some or all of the Advanced Export tools, with your own instructions. The safety rules above still apply, because Advanced Export enforces them itself. The Advanced Export agent's own instructions (checking queries before saving, saying where data comes from, asking when two people have the same name) are not part of the tools, so include anything similar your agent needs.
Other AI assistants (early access)
Any AI assistant that supports remote MCP servers can connect to Advanced Export. This uses an Atlassian feature that is in early access.
-
A site or organization admin enables it, once per site: in Atlassian Administration, go to Apps → Sites → your site → Connected apps, open Advanced Export, and turn on the tools you want to make available. It is off until an admin does this.
-
Add this server to your AI assistant:
https://mcp.atlassian.com/forge/c6231e4b-eac5-4d20-a312-9095a916d479 -
When the assistant connects, Atlassian asks you to sign in, choose the site, and approve access.
The same safety rules and limits apply. Some assistants do not ask before making changes the way Rovo does, but Advanced Export's own checks apply either way.
Data and privacy
The agent works on the same data as the rest of Advanced Export, processed in the region your admin chose. It does not add any new place where your data is stored: live previews are generated on request and not kept, and delivered files are the ones your schedules already store for download links. See Data Security and Privacy.
What you send to Rovo, and what the agent answers, is handled by Atlassian Rovo under Atlassian's terms.