Q: How do we know in advance when Forge will be rolled out for our org?
Answer
Automatic upgrades for all apps are currently paused. Once they resume, Atlassian selects which instances to upgrade at random, so Tempo cannot notify you in advance when it will roll out to your specific organization.
Q: What is the timeline for the Forge migration to complete? Is there any tentative date?
Answer
The timeline is on an app-by-app basis. Teams are currently monitoring fixes for Custom Charts and Structure, and a solution is being sought for Tempo for Jira issues before bulk upgrades resume.
Q: How can we perform the manual update? Wasn't it being rolled out without our control?
Answer
You can manually update your app today by going to Jira administration and clicking the "update" button next to the product name. The automatic, bulk upgrade is what Tempo has no control over in terms of which instances are chosen, but you retain control through manual update.
Q: What is the most efficient way to ensure that Forge is enabled on every single project in our Jira system?
Answer
Forge is enabled per application, per instance, not per project, so it is enabled for all projects by default. You can check the app version against the versions provided in our Forge documentation to confirm if your app is on Forge.
Q: As an Atlassian or IT administrator for my org, do I need to take any action for this change?
Answer
That will depend on which changes apply to your organization. For example, if your team uses Timesheets, updating the OAuth URL can minimize disruption. Most changes must happen once you are on Forge. As an admin, you can choose to manually update to control the timing of that migration.
Q: What steps do we need to take to continue using and ensuring our historical data is migrated?
Answer
No action is needed. Historical data, including accounts, work logs, and other configurations, is not affected by the migration.
Q: Will our Tempo apps be available on Atlassian Government Cloud or AGC?
Answer
Yes, Tempo is looking at AGC for all apps, but the timeline will vary by application.
Q: In case of disappearing account value, how fast are you going to solve the tickets you suggested we make?
Answer
The resolution speed depends on the issue. Certain fixes must come from Atlassian, which is why users are urged to reference the public tickets. Tempo is on "high alert" to resolve issues that the team can address internally.
Q: Do the JQL changes mean the filters used for dashboards, etc., will be broken until fixed?
Answer
Yes, once you move to Forge, dashboards using the old JQL syntax will break and will need to be updated.
Q: How can I fix broken JQL filters after migrating?
Answer
Use the Broken JQL Filter Finder feature under Tempo Settings once your instance is on Forge.
Q: Will we have access to that filter finder before migrating so we can prepare?
Answer
No, the Broken JQL Filter Finder is only available on Forge instances because it is designed to detect the old, broken syntax once the instance has migrated.
Q: Can we safely migrate from DC to Cloud with Tempo Timesheets data, or should we stay still?
Answer
For Timesheets, our current guidance on DC to Cloud migration is provided here.
Structure
Q: Why was Structure unavailable recently?
Answer
The root cause was a platform-level limitation from the Atlassian side, causing failures in generating Forge authentication tokens. A fix has been deployed.
Q: Can I still use a service account as a Structure owner?
Answer
No, this is still being investigated with Atlassian. Contact support if this is your case.
Q: What happened to my saved Structure links/bookmarks?
Answer
The URL format has changed. Old links will redirect, but it is recommended to save the new link format.
Q: How do I open Structure now?
Answer
The UI requires two clicks: the first opens the menu with Structure and Cross Team PI Planner, and the second click opens Structure.
Q: I use Tempo accounts or teams in my JQL insert rules for Structure. Do I need to do anything?
Answer
If you use Tempo accounts or Tempo teams in your JQL insert rules, you will need to manually update them.
Q: What are the new benefits of Forge for Structure?
Answer
Forge provides the following benefits to Structure:
The tab name now displays the Structure name.
Smart links are supported, allowing you to copy a Structure URL and paste it into Confluence to create a gadget.
Jira Teams are now supported in Gantt resources without formulas.
The Rovo assistant (formula creation agent) will be moved inside the app.
Custom Charts
Q: Why did Custom Charts experience an incident upon migration?
Answer
The issue, which impacted both Jira and Confluence, was due to the size of configurations in the gadgets being added to the backend communication token, exceeding AWS limits. It's fully resolved for Jira and largely resolved for Confluence.
Q: How do I edit a Custom Charts gadget in Jira now?
Answer
To edit a gadget after the Forge migration, go into Edit Your Dashboard first, and then you will be able to edit the gadget.
Q: Why do I see a pop-up when clicking external links?
Answer
For security, if external URLs are not explicitly defined in the manifest, a pop-up will notify you before taking you to another site.
Q: Are there any new features in Custom Charts on Forge?
Answer
A new Rovo agent is available, allowing you to use natural language to create charts, dashboards, or add them to existing dashboards without leaving your current context.
BI Connectors
Q: What happened to the Power BI Gadget?
Answer
The gadget was removed from the main application to better enable targeted functionalities through Forge. Its functionality is fully replicated by a new, free application available on the marketplace called Power BI Embed Reports.
Q: Are all APIs available in Forge for data scopes?
Answer
Not all APIs are available. Tempo is actively communicating with Atlassian to ensure they are present. Until then, you may use the current Jira API token.
Tempo for Jira (Timesheets, Capacity Planner, Financial Manager, and Tempo Core)
Q: What is important to remember when manually updating?
Answer
Don't forget to also update TempoCore, the companion app for Timesheets, Capacity Planner, and Financial Manager.
Q: What is the impact on JQL filter syntax?
Answer
The syntax has changed for account, tempo team, internal issue, and JQL filters using custom field IDs, which will be a breaking change for bookmarks, scripts, or automations.
Q: How can I fix broken JQL filters after migrating?
Answer
Use the Broken JQL Filter Finder feature under Tempo Settings once your instance is on Forge.
Q: What happened to operator support for Account and Tempo Team in JQL?
Answer
Equals and not equals are no longer available. Contains and not contains are now supported, but be aware that all properties within the field are searched.
Q: How do I log time from the Jira issue view after migration?
Answer
It is no longer possible to show the Tempo panel by default. Your admin must re-enable it on the Jira work item screen for each project. If the panel is missing from the right-hand sidebar, try toggling the time tracking provider in Jira settings.
Q: Did keyboard shortcuts for logging time (like 'W') change?
Answer
Yes, these shortcuts are no longer global on Jira. You must first open the command palette (Ctrl+K or Cmd+K) and then the shortcuts will work.
Q: Do saved Tempo report bookmarks still work?
Answer
No, saved Tempo reports used as bookmarks will no longer work. Recreate the report and re-bookmark/save it.
Q: Are there any new features in Tempo for Jira on Forge?
Answer
With the migration to Forge, our three Rovo agents are now available out of the box:
Timesheets work log assistant
Timesheet summary analyzer
Sprint performance assistant
The setup process for these agents has also been simplified and no longer requires a Tempo API token.
