Last updated: July 10, 2026
Below is a list of Active Atlassian tickets opened to address and monitor various issues related to the Forge migration. Also included is a list of Closed (or otherwise inactive) tickets for issues that have been fixed or have been confirmed by Atlassian to remain as-is. This page will be updated as new information becomes available.
We encourage you to reference these tickets in your own Atlassian support tickets to help expedite a resolution.
Active Tickets
|
Ticket |
Summary |
Atlassian updates as of July 10, 2026 |
|---|---|---|
|
Keyboard shortcuts and Command Palette entries may take 20-30 seconds to populate. |
No concrete timeline provided. |
|
|
Forge custom fields are rendered incorrectly in Jira JSPA pages. |
No concrete timeline provided. |
|
|
When a site or organization admin logs in as another user, Forge apps don’t work as expected. |
No concrete timeline provided. |
|
|
The Jira Time Tracking dialog opens instead of the Timesheets dialog when attempting to log work via shortcut on a Jira screen. |
No concrete timeline provided. |
|
|
Keyboard shortcuts are not loaded until the command palette is opened. |
No concrete timeline provided. |
|
|
Forge object type custom fields are incorrectly rendered when creating a linked issue using the legacy create modal. |
No concrete timeline provided |
Closed Tickets
|
Ticket |
Summary |
Ticket Resolution |
|---|---|---|
|
Bulk-editing is not supported for custom fields. |
Resolved by Atlassian on July 2nd. Bulk editing for custom fields is now fully supported. |
|
|
Tempo Account/Team fields can be hidden from some licensed Jira/Confluence users in Jira Service Management, if they belong to a |
Resolved by Atlassian on July 10. |
|
|
Forge Custom Fields don't set default values when creating a work item, and the Space has a default. |
Fixed on May 22. The default option will be set if no explicit option was provided during issue creation. |
|
|
Forge Custom Fields are broken on the transition screen. Tempo Team and Account fields render as plain text (instead of select) on classic Jira transition screens, with no validation. |
This ticket is closed as “Won’t fix.” The new transition experience will be rolled out to everyone in 6+ months. |