Upcoming Forge-related changes

Time to SLA for Jira Cloud will soon move to Atlassian’s Forge platform, a major infrastructure upgrade that ensures better performance, scalability, and security compliance with Atlassian’s latest standards.

This migration will introduce several important changes that may affect how you access and use Time to SLA.

We recommend reading through the details below to understand what’s changing and how to prepare. We’ll announce the migration through in-app announcements, so keep an eye out for updates directly inside Time to SLA.

On this page:

1 Key changes at a glance
2 SLA panel visibility
- 2.1 How to reopen the SLA panel for everyone (admins)
- 2.2 How to reopen the SLA panel in a work item (users)
3 Dynamic Calendar field change
- 3.1 🚨 Action required: Update automations or scripts that use this field
4 Need help?

Key changes at a glance

Area	What’s changing	What to expect

Area	What’s changing	What to expect
SLA panel visibility	Previously, the SLA panel appeared automatically when you opened a work item. After the move to Forge, the panel will be hidden by default due to platform limitations. You’ll still have full access to all your SLA configurations. Only the way you open the SLA panel will change.	Users can open it manually by clicking the Time to SLA button on the work item view. Admins can make it visible by default. For more information, refer to the instructions below.
Dynamic Calendar field change	The current Dynamic Calendar field will be replaced with a new Dynamic Calendar field created on Forge.	Because this field has a new field ID and now stores the calendar ID (instead of the calendar name), any automation rule, script, or integration that still references the old field ID or the old value format will stop working. To learn how to fix this, read the section below. If you rely on any any scripts or automations that set calendar values on work items, this is a breaking change. Please schedule time to update your configurations.
Periodic report links	Links in previously sent periodic report emails will stop working.	Emails sent before the migration contain outdated links that won’t open correctly. Emails sent after the migration will include new, fully functional links. No action is needed for future emails.
In-app links	The app’s internal URLs are changing with the move to Forge.	Any saved in-app links created before the migration will no longer work. If you’ve bookmarked any pages in the app, please update your bookmarks after the move.
Time zone handling	Time values in several areas will follow your device’s system time zone instead of your Jira profile settings.	This affects SLA start, target, and end dates shown on the SLA panel, SLA history tab, and Detail report. It also applies to the request creation dates shown on the recalculation, background reports, and periodic reports pages. These changes only affect how times are displayed, not how SLAs are calculated.
Mute SLA settings	The setting has been relocated.	Now found under Settings > General Settings > Apps > TTS Mute SLA.
Customer portal display	A SLA panel text may appear on the portal view even when no SLA is configured for that request type.	This issue is known and is being worked on by Atlassian.
Initial setup time (New installations)	A short waiting period will occur after installation.	After installing Time to SLA for the first time, users will need to wait around 3 minutes for the app to complete its initial setup. This delay is caused by Forge platform limitations and is expected behavior, so it does not indicate a performance issue.
SLA panel colors	Minor tone adjustments for visual consistency.	No functional changes.
Dynamic calendar	A new Create custom field button has been added.	Lets you create and link SLA time fields directly during goal creation.

SLA panel visibility

How to reopen the SLA panel for everyone (admins)

If you’re a Jira administrator, you can make the SLA panel visible on all work item pages by default.

Open any Jira work item.
Click the Time to SLA icon in the top menu.
- If you don’t see it, click the Jira ⋯ menu. The Time to SLA option may appear there, depending on the number of apps installed in your instance.
When the SLA panel section appears, click the ⋯ button next to it.
Select Show for all work items.

Once enabled, the SLA panel will appear automatically on all work items for all users in your project.

How to reopen the SLA panel in a work item (users)

If you’re not an administrator, you can still open the SLA panel for a specific work item.

Open a Jira work item.
Click the Time to SLA icon in the top menu.
- If you don’t see it, click the Jira ⋯ menu. The Time to SLA option may appear there, depending on the number of apps installed in your instance.

The SLA panel will appear on the work item view.

This enables the SLA panel only for the current work item. You can repeat this step on any work item where you want to use Time to SLA.

Dynamic Calendar field change

As part of our move to Forge Remote, we will introduce a new Dynamic Calendar field that replaces the existing Dynamic Calendar field used today. After the migration:

Your calendar data will be automatically migrated,
Your existing calendars continue working as before. However, the new field will have a completely different ID and stores a different value format, so you must update references in any automation or integration that uses it.

🚨 Action required: Update automations or scripts that use this field

If you set or read the Dynamic Calendar field in Jira Automation, ScriptRunner, REST API, or any integration, you must:

Use the new field ID
Use the calendar ID as the field value (instead of calendar name)

Follow the steps outlined below to perform these actions.

Step 1: Find your new Dynamic Calendar field ID

Go to Jira > Settings > Work items > Fields.
Search for TTS – Dynamic Calendar (MIGRATED).
Note the new field ID (for example, customfield_12345).

Step 2: Find your calendar ID

Currently, the Calendar ID is visible only in the calendar’s URL.

Open Time to SLA > Calendars
Click the calendar you want to use.
Look at the browser URL. It will include:

.../calendars/{calendarId}/view

Example:

dd8714a8-fc1a-4a47-8842-158e3993d042

Use this value in your automations and scripts.

Step 3: Update the Dynamic Calendar field value format

The new field no longer accepts calendar names. It must be set using the calendar ID.

Example JSON or payload pattern for setting the field value in automation/scripts:

{
  "fields": {
    "customfield_12345": "aaaa-zzzz-vvv-ddd"
  }
}

Replace customfield_12345 with the actual migrated calendar field ID.
Replace "aaaa-zzzz-vvv-ddd" with the calendar ID of the calendar you want to set on the work item.

Need help?

If you have any questions or feedback about the migration, contact our support team.