Capacity Planner (Cloud)
Capacity Planner (Cloud)
Breadcrumbs

Capacity Planner Migration to Forge FAQs

To support you throughout the ongoing Forge migration process, we’ve compiled a list of the most frequently asked questions based on customer feedback. This FAQ page is designed to provide quick, easy access to the latest information.

How to Check Your Current Version

Question: How can I tell if my instance is already on Forge?

Answer: Check your app version by navigating to Jira Settings → Marketplace Apps. The following versions indicate a Forge installation:

Capacity Planner and Tempo Core

  • Capacity Planner: 5.0.0+

  • Tempo Core: 6.0.0+

Other Tempo Products

  • Timesheets: 5.0.0+

  • Financial Manager: 5.0.0+

  • Structure PPM and Gantt Charts for Structure PPM: 5.0.0+

  • Custom Charts for Jira: 11.0.0+

  • Custom Charts for Confluence: 9.0.0+

  • Power BI, Big Query, and Looker Studio Connectors: 4.0.0+

  • Tableau and SQL Connectors: 5.0.0+

  • Time Tracker: 4.0.0+

Migration Timing & Process

Question: Will the upgrade happen automatically, or can we choose when it occurs?

Answer: Upgrades are rolled out automatically in random batches. Tempo cannot control which sites are included or when they are included. You can manually trigger the upgrade before the automated rollout reaches you via Jira Settings → Marketplace Apps → View App Details → Update.

If you manually update Capacity Planner, you must also manually update Tempo Core at the same time (see below).


What is Tempo Core, and do I need to update it?

Tempo Core is the free, base application that powers Timesheets, Capacity Planner, and Financial Manager. It must be updated alongside your other Tempo apps.

Automatic upgrade: Tempo Core will be updated automatically during the automatic rollout for Capacity Planner. But if you are manually updating Capacity Planner, you must also update Tempo Core.

Manual upgrade: If you’re manually updating Capacity Planner, you must also go to your Jira Connected Apps, find "Tempo Core" and click Update.

Refer to the Expected Changes documentation for the latest updates.


Question: Will we be notified of our instance migration in advance?

Answer: Tempo has no visibility into which instances are scheduled next. You can check your app version to confirm whether your instance is already on Forge. Otherwise, you can manually trigger the upgrade before the automated rollout reaches you via Jira Settings → Marketplace Apps → View App Details → Update.


Question: Can we delay the migration until known issues are fixed?

Answer: Our announced tentative automatic rollout date accounts for Atlassian’s timelines to key fixes. We are monitoring key fixes on this page and will share the latest updates there.


Question: How long does the migration take? Is there any downtime?

Answer: No downtime or performance issues are expected during the upgrade.


Question: Can we upgrade our sandbox environment before production to test the impact?

Answer: Yes, you can upgrade sandbox and production environments independently, which allows you to test the impact of changes — such as broken JQL filters — before upgrading production.

DC to Cloud Migration


Question: Do these changes apply to Jira Data Center?

Answer: No. Forge is specific to Atlassian Cloud. There are no changes to existing Data Center apps.


Question: Can we migrate from Data Center to Cloud right now?

Answer: For Capacity Planner, our current guidance is the following:

For DC customers with migrations planned between now and May 31 

For DC customers with migrations planned for June 1 onwards (or have not planned or started): 

If you have any questions, we recommend contacting Tempo Support to review all factors before proceeding.


Question: If we migrate from DC to Cloud now, will any data be lost?

Answer: No data is lost during a DC to Cloud migration. Depending on the app, there may be some functional or UI changes to be aware of, covered in our Expected Changes documentation.


Data Center Users

Question: Do these changes apply to Jira Data Center?

Answer: No. Forge is specific to Atlassian Cloud. There are no changes to existing Data Center apps.

API & Authentication Changes

Question: Are there any changes to Tempo API endpoints?

Answer: No, API endpoints are not changing. The only authentication-related change is to the OAuth URL format.


Question: Where and how do we update the OAuth URL?

Answer: Details on the updated OAuth URL format are here. Note that the new URL supports both Connect and Forge, so you can update it before upgrading the app.


Question: Will API tokens be affected by the Forge migration?

Answer: No, API tokens are not affected by the Forge migration.


JQL Filters and Automations

Question: Will existing JQL filters break after the migration?

Answer: Some JQL filters will break if they reference Tempo-specific fields such as Account, Tempo Team, internal issues, or custom field IDs. A Broken JQL Filter Finder tool is available after upgrading to Forge to help identify and fix affected filters.


Question: Will Jira dashboard filters be affected?

Answer: Yes, dashboard filters using broken JQL will be affected. Once you fix the broken JQL, they will work again.


Question: Will the Broken JQL Filter Finder also find private filters?

Answer: The Broken JQL Filter Finder shows all the filters a user has permissions to. As a Jira admin, you can also view Private filters. This feature uses overrideSharePermissions, an experimental flag available to users with Administer Jira global permissions that overrides share permissions to enable filters to return any share permissions.

Question: Will Jira Automations using Tempo fields in JQL be affected?

Answer: Some automations referencing Tempo Account fields in JQL might need to be updated after the Forge migration. Please refer to the Automations section of the Expected Changes documentation.

Data & Historical Records

Question: Will historical worklogs, plans, and reports be preserved?

Answer: Yes, there are no changes to historical data, worklogs, or plans.

UI & Time Tracking Changes

Question: Will the day-to-day experience of logging time change significantly?

Answer: Not significantly. There are some minor UI/UX differences, and a few specific logging methods are affected, such as the Jira issue view Tempo panel and keyboard shortcuts. All other ways of logging time remain the same.

Question: Will the time tracking panel on Jira issues (showing Estimated, Remaining, and Logged time) still be available?

Answer: Yes, that panel will still be available after the Forge migration. Contact Tempo Support if it is missing after your upgrade.


Question: Will my saved Tempo Report bookmarks still work after the Forge migration?

Answer: No, saved report bookmarks will no longer work after the upgrade. Here's what to do:

  • Before upgrading: Open each bookmarked URL and save the report.

  • After upgrading: Recreate the report and re-bookmark or re-save it.

Third-Party Integrations & Add-ons

Question: Will third-party apps and connectors that integrate with Tempo be affected?

Answer: If the integration uses Tempo's API directly, it should not be impacted. If it relies on OAuth URLs, the format needs to be updated to the new URL format. If JQL filters reference Tempo fields, those filters will need to be updated. We recommend that you contact the third-party vendor's support for confirmation.

Jira Service Management (JSM)

Question: Does the Forge migration affect Jira Service Management projects?

Answer: Potentially yes. If you are using hidden Tempo fields in JSM request types, these may be affected. This is one of the blockers Tempo is actively pushing Atlassian to resolve before automated upgrades resume.