Changelog

Jira custom field and custom field type modules are now available on the new create issue dialog.

See Jira custom field and Jira custom field type documentation for more details.

We're deprecating the epic link, parent link, epic, and other related fields and events in the Jira REST API and webhooks. They will be removed from the REST API and webhooks on 31 May 2022.

The scope of this change is the Jira REST API and webhooks only. The deprecation does not apply to these fields in Jira UI.

For a breakdown of the affected operations and webhooks, see the announcement in the Developer Community.

Jira custom field and custom field type modules now support the new datetime data type. This enables the usage of dates with both time and timezone in both modules.

See Jira custom field and Jira custom field type documentation for more details.

As part of the work to support team-managed projects having multiple boards, we’re deprecating the GET /rest/agile/1.0/project/{projectIdOrKey}/features endpoint.

By May 9, 2022, this endpoint will no longer work. Instead, you’ll need to use the new GET /rest/api/1.0/project/{projectIdOrKey}/features endpoint instead. This new endpoint only returns project features.

We’re also making some changes to the following existing endpoints:

• The GET /rest/agile/1.0/board/{boardId}/features endpoint currently returns all features. By May 9, 2022, this endpoint will only return board features.

• The PUT /rest/agile/1.0/board/{boardId}/features is currently used to toggle the state of features. By May 9, 2022, if you want to toggle project features, you’ll need to use the PUT /rest/api/1.0/project/{projectIdOrKey}/features/{featureKey} endpoint instead.

We’ve restructured the Modules and UI kit components reference documentation, to make it easier to navigate and consume content.

Added Custom UI support for defining the editing experience for Jira custom fields and Jira custom field types.

Added Custom UI support for Jira context configuration of custom fields.

The context configuration function of the Jira custom field type module now returns the CustomFieldContextConfig component. It can be used to render a configured view of the field in a custom field context.

Run npm install @forge/ui@latest in your resource directory to install the latest version of the UI kit.

The formatter property of the Jira custom field and Jira custom field type modules is now used on an issue view when a rendering function is not defined for a field. This formatter property renders the value as a string.

Forge custom fields are now supported on the create issue dialog for modules that have rendering and editing functions defined.

See custom field issue creation for more details.

As team-managed projects in Jira Software only support one board, the ability to delete the board from a team-managed project has been removed from the Delete board operation. The operation continues to support the deletion of boards from company-managed projects. See the developer community post Change notice: DELETE Board API in Jira Software team-managed projects for more details.

Custom field values are no longer stored in issue properties since there is now a dedicated REST API for updating values directly. This means it's no longer necessary to define an issue property key for them.

By 1 June 2021, the previous method of defining custom field values will no longer be supported.

See Jira custom field module for more details.

Classic and next-gen projects in Jira now have new names that are clearer and more descriptive of their corresponding project types:

• Next-gen projects will be named team-managed projects. The functionality itself remains the same and will continue to be ideal for independent teams who want to control their own working processes and practices in a self-contained space.

• Classic projects will be named company-managed projects. Set up and maintained by Jira admins, company-managed projects will remain the best choice for teams who want to work with other teams across many projects in a standard way, such as sharing a workflow.

Learn more about how we're simplifying project creation in Jira.

From 1 April 2019 the paginated operations for filters and projects must be used.

See Removal of non-paginated project and filter endpoints from REST API v2 for more detail.