Migration from Atlassian Connect to Atlassian Forge platforms
What is happening?
Atlassian is retiring the older “Connect” framework that many Jira Cloud apps, including Repeating Issues, were originally built on, in favor of their newer Forge platform. We are migrating Repeating Issues to Forge to keep the app supported and compliant with Atlassian's platform requirements.
This is a behind-the-scenes infrastructure change. It does not change how the app looks or works for you.
Latest version of our app is already 90% Forge app. Please update.
What do you need to do?
In most cases: nothing.
The migration happens automatically as part of a regular app update. To make sure you get it smoothly, we recommend:
Keep the app set to auto-update in your Jira instance (this is the default for Cloud apps).
If you manage updates manually, please install the latest version of Repeating Issues when it becomes available.
No reconfiguration, no data re-entry, and no re-authorization should be required — your schedules, calendar rules, and settings will carry over.
We will notify you here and via the app's release notes once the migration is fully complete for your site.
Will anything look or behave differently?
You may notice:
Some screens may ask you to accept a small number of additional or updated permissions the first time you open them after the update — this is a normal, one-time part of moving to the new platform and does not mean the app is asking for more access to your data than before.
Minor visual refinements, as parts of the app are now rendered using Atlassian's newer UI components.
Core functionality — repeating/cloning issues, calendar rules, settings, and reporting — remains unchanged.
Risks and what we're doing about them
We take this migration seriously and are rolling it out carefully:
Risk | Our mitigation |
|---|---|
Temporary disruption during cutover | Migration is staged and tested on internal and staging environments before being released broadly. |
Data continuity (schedules, rules, settings) | All existing data stays in place; the migration only changes how the app connects to Jira, not where your data lives. |
Permission changes | New permission scopes are limited to what's strictly needed and reviewed against Atlassian's guidelines before release. |
If you experience any issue with the app before, during, or after this change, please reach out to us through our https://codedoers.atlassian.net/servicedesk/customer/portal/1/group/1/create/1 and we will prioritize it.
Our plan
We are completing the migration in stages, moving one part of the app at a time to Forge, so that most of the app is already running on the new platform today.
We are validating each stage with internal testing before it reaches customers.
We plan to complete the full migration well ahead of Atlassian's deprecation deadline for Connect apps, so there is no risk of service interruption caused by Atlassian retiring the old platform.
We will keep this page updated with progress and let you know if any action is ever required on your side.
Questions?
Contact us any time via the https://codedoers.atlassian.net/servicedesk/customer/portal/1/group/1/create/1 — we're happy to answer any questions about this change.