Forge custom fields of type object now support a rich edit experience in Jira issue bulk edit

What's changing

Forge custom fields (FCF) of type object can now render a rich custom edit experience in Jira's bulk edit.

Previously, object type FCF were rendered as an empty text input via (Atlaskit's TextField). With this change,

• It will be rendered as an empty JSON schema, making it easier to inline edit.
• You can now control how the field renders during bulk edit using your own custom resources via UI Kit or Custom UI, consistent with other surfaces such as issue view and global issue create.

This is available as a Preview feature, and currently only for the object field type.

What you need to do

• To opt in to the bulk edit experience, add issue-bulk-edit to the edit experiences of your custom field (or custom field type) in your manifest.yml: ```

modules: jira:customField:

• key: my-object-field name: My object field type: object edit: experience:
  • issue-create
  • issue-transition
  • issue-bulk-edit // <-- new surface

```

• Keep these constraints in mind for the bulk edit experience:
  • Issue and Project details are not available in the extension context during issue-bulk-edit.
  • In the formatter expression, only value and fieldId are available when renderContext/experience is issue-bulk-edit.
  • If your edit UI depends on issue or project context, detect this case using renderContext === 'issue-bulk-edit' and render an appropriate fallback UI.

For details, see: Jira Custom Fields > Issue Bulk Edit.