GUID: CHANGE-3329
pubDate: Tue, 08 Sep 2026 04:41:53 GMT
Category: Added
What's changing
Follow-up to CHANGE-3253 (rich edit experience for object-type Forge custom fields in Jira bulk edit). Previously, issue and project details were not available in the extension context when renderContext === 'issue-bulk-edit', and Atlassian recommended detecting that render context and showing a fallback UI. That limitation is now removed: issue and project context is populated in the app's extension context during bulk edit. Apps that shipped a fallback UI can now read the issue/project context instead. The jira:customField extension-data reference has been updated with the new context shape (note: bulk edit context carries an issues array, plural, rather than a single issue).
Parity impact for forge-sim
Area: modules / extension context (renderer + forge_ui_render/forge_invoke context hydration). If forge-sim simulates the jira:customField edit surface with renderContext: 'issue-bulk-edit', the simulated extension context should now include issue(s) and project data in that render context instead of omitting them. An app written against the new behavior (reading issue/project context during bulk edit) should work in forge-sim; an app relying on the old "context absent" detection pattern still works either way. Check the extension-data reference for the exact bulk-edit context shape:
https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#extension-data
Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3329
GUID: CHANGE-3329
pubDate: Tue, 08 Sep 2026 04:41:53 GMT
Category: Added
What's changing
Follow-up to CHANGE-3253 (rich edit experience for object-type Forge custom fields in Jira bulk edit). Previously, issue and project details were not available in the extension context when
renderContext === 'issue-bulk-edit', and Atlassian recommended detecting that render context and showing a fallback UI. That limitation is now removed: issue and project context is populated in the app's extension context during bulk edit. Apps that shipped a fallback UI can now read the issue/project context instead. The jira:customField extension-data reference has been updated with the new context shape (note: bulk edit context carries anissuesarray, plural, rather than a single issue).Parity impact for forge-sim
Area: modules / extension context (renderer +
forge_ui_render/forge_invokecontext hydration). If forge-sim simulates thejira:customFieldedit surface withrenderContext: 'issue-bulk-edit', the simulated extension context should now include issue(s) and project data in that render context instead of omitting them. An app written against the new behavior (reading issue/project context during bulk edit) should work in forge-sim; an app relying on the old "context absent" detection pattern still works either way. Check the extension-data reference for the exact bulk-edit context shape:https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#extension-data
Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3329