Expected Changes in Capacity Planner on Forge

Capacity Planner is moving from the legacy Atlassian Connect framework to Forge, Atlassian’s modern, secure, and scalable cloud app platform. This upgrade improves the security, reliability, and long‑term compatibility of Capacity Planner with Atlassian Cloud.
This document outlines the user experience and behavioral changes associated with this transition so users understand what to expect. If you encounter any interface or behavioral changes not covered on this page, please let us know.

New JQL Filter Syntax

Some JQL filters will require updated syntax after transitioning to Forge. Existing saved filters that use the old syntax, such as links and bookmarks, will no longer work.

Once your instance is on Forge, please update your filters to use the new syntax as soon as possible.

Account Syntax

The Account custom field must be changed to Account.name. See below for examples.

Operator	Old syntax	New syntax
`=`	`Account = "Maintenance"`	`Account.name = "Maintenance"`
`!=`	`Account != "Maintenance"`	`Account.name != "Maintenance"`
`IN`	`Account IN ("Maintenance", "Research")`	`Account.name IN ("Maintenance", "Research")`
`NOT IN`	`Account NOT IN ("Maintenance", "Research")`	`Account.name NOT IN ("Maintenance", "Research")`

“Tempo Team” Syntax

The "Tempo Team" custom field must be changed to "Tempo Team.name". See below for examples.

Operator	Old syntax	New syntax
`=`	`"Tempo Team" = "Palavin"`	`"Tempo Team.name" = "Palavin"`
`!=`	`"Tempo Team" != "Biotics"`	`"Tempo Team.name" != "Biotics"`
`IN`	`"Tempo Team" IN ("Development", "Research")`	`"Tempo Team.name" IN ("Development", "Research")`
`NOT IN`	`"Tempo Team" NOT IN ("Alpha", "Delta")`	`"Tempo Team.name" NOT IN ("Alpha", "Delta")`

Internal Issue Syntax

issue.internal must be changed to issueInternal. For example:

Old syntax: issue.internal = 'TRUE'
New syntax: issueInternal = 'TRUE'

Contains (~) and Not Contains (!~) Operator Support for Account and “Tempo Team”

Account and "Tempo Team" now support contains (~) and not contains (!~) operators, as described in the table below.

Old behavior

New behavior

Account and "Tempo Team" did not support the contains (~) and not contains (!~) operators.

Account and "Tempo Team" now support contains and not contains operators. However, it is important to note that all properties are searched.

Example: There is an account called Maintenance with an Account Category of OPEX.

When using contains (~) or not contains (!~) in either Basic or JQL mode, it searches all properties within the Account.

In the above example, when searching for Account ~ OPEX, the account Maintenance will appear, even though OPEX is an Account Category, a property of Account.

contains and not contains operators-20260326-183559.png

The JQL will find those properties because they are contained (or not contained) within the Account.

Recommendation:

For more specific filter results, use other operators and account property-specific JQL syntax. For example, to filter by account name, use Account.name = "Maintenance" .
View the list of supported Tempo JQL functions here: https://help.tempo.io/timesheets/latest/tempo-jql-functions-for-advanced-jira-search

Changes to JQL custom field IDs

Old behavior

New behavior

JQL filters using custom field IDs used to work for these operators:

=
!=
IN
NOT IN

Example: cf[10000] = "Maintenance"

Only the contains operator (~) is supported. For example, cf[10000] = "Maintenance" is not available.

All JQL filters using custom field IDs with other operators must be updated to the new syntax.

Custom fields IDs never supported property fields. For example, cf[10000].name =
"Maintenance" was never possible on Connect and is neither possible on Forge.

Changes to Keyboard Shortcuts Behavior and New Keywords

Previously, Tempo supported global keyboard shortcuts that worked anywhere in Jira and Tempo:

W: Opens the Log Time
G then T: Opens Tempo Capacity Planner in either Team Planning or Resource Planning view, depending on the user’s preference.

These shortcuts worked instantly without any setup or additional UI interaction.

Now on Forge Remote, keyboard shortcuts are no longer global. They are now implemented as Atlassian Command Palette actions, and you must open the command palette once before keyboard shortcuts work.

To use Tempo shortcuts in Jira views:

Open the Command Palette:
1. Cmd + K (Mac)
2. Ctrl + K (Windows)
Use the shortcuts.
Alternatively, use these supported keywords:

Tempo
Timesheets
Financial Manager
Capacity Planner

Important: Command palette shortcuts are only fetched after the user opens the palette for the first time. This means shortcuts are not available immediately on page load. They only become active after opening the Command Palette once per session.

To use Tempo shortcuts in Tempo views:

Keyboard shortcut behavior in Tempo views remains unchanged.

OAuth Changes

The URL to authorize OAuth apps will change as indicated below.

Before
`GET: https://{jira-cloud-instance-name}.atlassian.net/plugins/servlet/ac/io.tempo.jira/oauth-authorize/?client_id=$CLIENT_ID&redirect_uri=$REDIRECT_URI` This old URL will work only on Connect.
After
`GET: https://api.tempo.io/oauth/authorize/redirect?client_id=$CLIENT_ID&redirect_uri=$REDIRECT_URI&jira_url=https://{jira-cloud-instance-name}.atlassian.net` This URL will work for both Forge and Connect.

Before

GET: https://{jira-cloud-instance-name}.atlassian.net/plugins/servlet/ac/io.tempo.jira/oauth-authorize/?client_id=$CLIENT_ID&redirect_uri=$REDIRECT_URI

This old URL will work only on Connect.

After

GET: https://api.tempo.io/oauth/authorize/redirect?client_id=$CLIENT_ID&redirect_uri=$REDIRECT_URI&jira_url=https://{jira-cloud-instance-name}.atlassian.net

This URL will work for both Forge and Connect.

In Forge, an authorization page showing "Access denied" now displays if the user doesn’t have permission to access Timesheets, Planner, and/or Financial Manager.

Firewall Configuration

If you are unable to access Tempo apps, your firewall may be blocking traffic from Atlassian's Forge platform and its CDN domains. Atlassian controls these domains and may update them at any time.

Allow the following Atlassian domains in your firewall to prevent these issues.

Other UX Changes

Bookmarks will be automatically redirected from the old URL to the new URL redirect provided by Atlassian.
After authorizing an OAuth App, upon clicking the Onwards! button, the redirect URI will now open in a new tab.
Notifications will now appear in the bottom-left corner instead of the upper-right-hand corner.

notifications placement-20260112-191624.png

Left-clicking on an external link prompts you to confirm navigation to the external site.

All links on the apps page (e.g. trial links, open app, instructions for integrations, installation of integrations, etc.) will open in new tab.

Spinners display across modals and iFrames to visually indicate that a loading action is in progress.