Issues and Projects context are now available in Forge Custom Field on Issue Bulk Edit
- Announced
- APIs
- forge-core-platform, forge-jira-cloud-platform
- Severity
- notable, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3329
What's changing?
In https://developer.atlassian.com/changelog/#CHANGE-3253, we announced that Forge custom fields (FCF) of type object can now render a rich custom edit experience in Jira's bulk edit. At that time, issue and project details were not available in the extension context during issue-bulk-edit, and we recommended using renderContext === 'issue-bulk-edit' to detect this case and render a fallback UI.
This limitation has now been removed. Issue and project context is now available in your app's extension context during bulk edit. You can use this context to make more informed decisions about the UI or the options you display.
What do I need to do?
- If you previously added a fallback UI for the
issue-bulk-editrender context, you can now update your app to use the available issue and project context instead. - Review the updated https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#extension-data:~:text=module%20is%20rendered.-,issues,-issue%5B%5D for details on the context shape.
- No action is required if your edit experience does not depend on issue or project context.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.