Moving to Atlassian Forge

What changes for your Jira Cloud site, and what does not

Moving to Atlassian Forge

Flower for Jira Cloud is moving from Atlassian Connect to Atlassian Forge. Forge is the platform Atlassian builds all new apps on, and Connect is being phased out (end of support: January 31, 2027). For you, this is an update of the same app: same name, same listing on the Atlassian Marketplace, same license.

What stays the same

• Your data. Flower keeps everything in Jira (work items and their properties). The update does not move or copy it.
• Your running processes. Process instances that are running continue where they stopped.
• Your models and settings. Models, the Jira work type mapping and the Flower settings are taken over on their own. You do not enter them again.
• Your license. A paid license stays paid, an evaluation continues. The update does not start a new trial and does not ask you to buy again.
• Your REST API calls. The public Flower REST API keeps working with your API token.

What gets better

• Security. Forge runs inside Atlassian’s infrastructure. Atlassian handles authentication, the app only gets the permissions it asks for, and every update is reviewed by Atlassian.
• Your data stays with Atlassian. The app runs inside Atlassian’s infrastructure and keeps its data in your Jira.
• Fewer moving parts. The process engine runs in Atlassian’s cloud next to your Jira.
• A future-proof app. Connect receives no new features and its end of support is set. Forge is where Atlassian invests.

What you need to do

Most sites need one click.

1. A Jira administrator opens Apps > Manage apps (or the Marketplace page of Flower) and sees an Update for Flower.
2. Atlassian may show a screen to approve the permissions of the app. This is the standard Atlassian screen, you only need to read it and confirm.
3. After the update, open Flower once. Your repository, models and settings are there. That is all.

If you do nothing, your site keeps running the current Connect version until you update. We recommend to update well before Connect reaches its end of support.

Frequently asked questions

Do I lose anything during the update? No. The data is in Jira and is not touched. The update replaces the app, it does not delete anything.

Is there downtime? Flower may be unavailable for a few minutes while the new version is installed. Running processes continue afterwards.

What happens to a process that is running while I update? It continues after the update. Timers keep their due dates.

Who has to do the update? A Jira administrator of your site.

What if I have an evaluation or an app that is installed but not used? Nothing happens on its own. The update is offered like any other, and the evaluation continues after it.

Does the update change my users or their permissions? No. Flower works with the permissions Jira gives your users.

Does Flower send data to other companies? Usage analytics (anonymous, without names, accounts, titles or content) can be switched off in the Flower settings, tab Analytics.

I use the Flower REST API. Do I need to change anything? No. Use your Jira e-mail and API token as before.

Can I go back? Rolling back to the Connect version is not possible by yourself. If you have a problem after the update, contact us (see below) and we help.

Where do I get help? Write to support . We are glad to do the update together with you.

Timeline