🚀 Time to SLA for Jira Cloud is moving to Forge

[#1]

Hello, Atlassian Community! This is Derya from Appfire.

We have an important update to share about Time to SLA for Jira Cloud. Atlassian is requiring all Marketplace apps to move to the Forge platform, their newest Cloud app framework, and that includes us!

The migration brings long-term benefits, and while most of it is under the hood, you’ll notice a few changes in how the app behaves.

There’s nothing you need to do right now. We’re simply sharing the key changes in advance to help your teams prepare.

The 3 most important changes

These are the updates you’re most likely to notice in daily use.

1. SLA panel visibility behavior will change

The SLA panel will no longer open automatically when you view a work item, as this behavior isn’t supported on Forge.

• Jira admins can make the panel visible for all work items by default. The steps are outlined in our documentation.

• Individual users can open the SLA panel at any time using the Time to SLA button in the work item view.

Your SLAs, goals, and calculations are not changing; only how the panel shows up.

2. Older report email links won’t work

Links in emails sent before the migration will stop working because they use the old URLs.

• New emails sent after the migration will include updated links that work as expected.

• Reports themselves are not affected; only the old email links are.

3. SLA panel text in the customer portal

In Jira Service Management, you will see the SLA panel text in the customer portal even for request types that don’t use SLAs.

• This is a known Forge limitation.

• Atlassian is actively working on improving this behavior.

• It doesn’t affect how your SLAs run or how your requests are handled.

A few smaller adjustments will also come with the migration, including a new location for Mute SLA in the Jira settings and minor visual tweaks to SLA panel colors.

You can find the full list and details in our documentation.

We’d love your feedback

We’ll be monitoring the impact of these changes, and your feedback will inform our improvements. Feel free to:

• Comment below

• Ask questions

• Tell us how you feel about these changes

[Onder Ozcan]

Hi Derya,

Thanks for sharing this. Forge is the future, and Time to SLA is part of this exciting future.

I can't wait to deliver this version to our customers.

Cheers,
Onder

[carl]

It’s good to know that the migration to Forge won’t affect SLA calculations or goals — just how the panel displays.
The change to panel visibility makes sense given Forge limitations, and it’s helpful that admins can set it for all work items by default. The note about older email links breaking is important for teams relying on past notifications, so it’s good to plan for that

[Oksanа]

Congrats on the move to Forge! When are you planning to release/present your add-on as fully Forge (full Forge) compatible? Curious about your timeline)