Forge migration plan
The migration is complete: the latest version of Advanced Export runs entirely on Atlassian Forge, with no Connect components, and it will keep working after January 2027. There is no plan to discontinue the app. Updating to it asks an administrator to approve a set of permissions — all of them read-only — and this section explains exactly what they cover and what happens if you do not.
If you administer Jira, you may have seen a message like this next to Advanced Export on the Connected apps page in Atlassian Administration:
This app may stop working after January 2027, as it's running on a platform that will be unsupported from that date.
This page explains what that message means, why it appears for our app, and what we are doing about it.
Why you are seeing this message
Atlassian is retiring Atlassian Connect, its older app platform, on 31 January 2027. It is replaced by Forge, the modern platform. To help administrators plan, Atlassian now shows a notice on every app that still uses any part of Connect.
Advanced Export has already moved to Forge. Everything you interact with — the dashboard, the export screens, the board and backlog actions, the admin settings, authentication and permissions — runs as a native Forge app today.
If your site has not yet approved the latest update, it is still running an earlier version in which a small internal component uses a Connect interface. It is not something you see or use directly: it is the mechanism our backend uses to authenticate to your Jira site when generating scheduled reports. Because that component exists in the version your site runs, Atlassian's automated check classifies the app as "using Connect", and shows the notice. Approving the update removes it.
The notice is generated automatically from that classification. It is not an assessment of our app specifically, and it is not a signal that we have stopped maintaining it.
The update that asks for your approval
The update that completes the migration changes how our backend authenticates to Jira: away from the Connect mechanism Atlassian is retiring, and onto Forge's own tokens. Forge grants access through explicit, itemised permissions, so the new version has to ask for a set of them — and Atlassian requires an administrator to approve any update that does.
You will see the usual Atlassian prompt on the Connected apps page, listing the permissions and asking you to approve the update. Nothing changes for your users until you do.
What is being asked for
Every permission that touches your Jira data is read-only. The app cannot create, edit or delete anything in Jira, and none of these permissions lets it do so.
| What the app asks for | What it is used for |
|---|---|
| Read issues, fields, projects, filters and boards | Building the exports themselves |
| Read user details and email addresses | Naming people in reports, and delivering reports by email |
| Check what a user is permitted to see | Making sure a scheduled report never contains more than its author could see in Jira |
| Read Assets objects (Jira Service Management) | Including Assets fields in exports |
| Platform tokens | Letting scheduled reports run when nobody is signed in |
Most of these are the Forge equivalents of access the app already has through Connect today — they look new only because Forge itemises what Connect granted in one block. Two are genuinely new: checking a user's permissions, and reading Assets objects.
Why the permission check is there
Scheduled reports run in the background, hours or days after anyone last opened Jira. They run as the person who created the schedule, so the report contains exactly what that person can see — no more.
Preserving that under Forge is what the permission-checking access is for. It is a privacy control rather than a broadening of access: without it, a background report would have to run with the app's own permissions, which are wider than any individual's.
What happens if you do not approve
Nothing breaks. Your site stays on the version you have now, and it keeps working exactly as it does today.
Two things to know:
- The Atlassian end-of-support notice will remain on your Connected apps page, because your site is still running the version that uses Connect.
- Connect support ends on 31 January 2027. The update needs to be approved before then.
Once you approve, the notice disappears from the Connected apps page.
There is no rush on any particular day, and no penalty for taking time over an internal review. If you need documentation for one, please ask us — we would rather send you what you need than have you approve something you have not read.
What approving does not do
- It does not require you to reinstall the app.
- It does not affect your saved exports, templates, schedules, permissions or settings.
- It does not interrupt scheduled reports.
- It does not change where your data is processed — that stays as you set it in App Settings.
Will the app stop working?
No. The migration was completed in September 2026, well before the January 2027 deadline, and the latest version passes Atlassian's own Connect-removal check with no remaining Connect components.
There is no plan to sunset Advanced Export. It remains actively developed and supported.
Will I need to do anything?
One thing: approve the permissions update described above, at whatever point suits you before 31 January 2027.
Beyond that, no.
- You will not need to reinstall the app.
- You will not lose your saved exports, templates, schedules or settings.
- Your scheduled reports will continue to run without interruption.
Each release is recorded in the changelog.
Our timeline
| Phase | Status |
|---|---|
| Move the user interface, authentication and permissions to Forge | Complete |
| Publish our migration commitment to Atlassian | Complete |
| Build and test backend Jira authentication on Forge tokens | Complete |
| Replace the remaining Connect lifecycle component | Complete |
| Release the update that asks administrators to approve new permissions | Complete |
| Remove all Connect components; Atlassian notice disappears | Complete — September 2026 |
The one remaining step is yours: approving the update on your site, at any point before 31 January 2027.
Why Advanced Export uses its own backend
A question that often comes up alongside this one: why does the app have a backend server at all, rather than running entirely on Atlassian's infrastructure?
Several of the app's core features cannot be provided by the Forge runtime alone:
- Scheduled reports that run on a recurring cadence, independently of anyone's browser session.
- Large exports that take longer to generate than Forge's function time limit allows.
- Delivery to your systems — uploading report files to your SFTP server, or sending them through your own email provider.
- Temporary file storage for download links and API access, retained for the period you choose.
For these cases Atlassian provides Forge Remote, a supported part of the Forge platform that lets a Forge app delegate work to a backend operated by the vendor. This is the documented and recommended approach for apps like ours, and it is unaffected by the Connect end-of-support timeline.
You choose the geographic region in which that processing happens — see App Settings. Details of what is stored, where, and for how long are in our Data Security and Privacy Statement.
Questions
If you have questions about this migration, or you need something in writing for an internal review, please contact our support team. We are happy to help.