Below is a list of Atlassian tickets opened to address and monitor various issues related to the Forge migration. 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.
|
Ticket |
Summary |
Atlassian updates as of May 29, 2026 |
|---|---|---|
|
ECOHELP-122513 |
Tempo Team and Account fields can't be used as a hidden field with a default option. |
A fix was implemented by Atlassian on April 30th. Note the following:
|
|
Bulk-editing is not supported for custom fields. |
Available mid-June. |
|
|
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. |
|
|
The Time entry panel no longer appears in the Jira issue sidebar after migrating to Forge. |
Status: Not being considered Atlassian recommends using this API to allow Jira admins to configure Issue Panels at scale. |
|
|
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. |