Changelog

In the developer console, you can now edit the title and description of your app alert, as well as view alert history. You can also see the metrics highlighted when value is below the threshold. For more information, see Manage app alerts.

We have added a new optional query parameter, accessType to the bulk get groups API to return only groups with a specific type of permission based on the accessType provided. This is an enhancement to the existing bulk get groups (GET /rest/api/3/group/bulk) API in Jira to support fetching groups.

Endpoint: GET /rest/api/3/group/bulk

Query parameter: accessType

Values: site-admin, admin, user.

Returns: name (name of the group) and groupId (group identifier)

If your apps have hardcoded references to group names, particularly for default groups (for example, site-admins, jira-admins-<tenantName>) in their configurations, it is recommended to start using this API to get groups to ensure your app continues to work for all customers.

The name field in the Jira REST API operations that include group details is deprecated and replaced with groupID.

We’re changing this to enable support for functionality to rename groups. To achieve this, groups need an immutable identifier rather than the inherently mutable group name identifier. Thus, we’re removing the use of group name as the identifier and replacing it with groupID.

The name field will be removed on 28 February 2023.

See the Adding support for groupID field in Jira REST APIs, expressions types developer community post for more details on the change.

To help you debug your Forge apps, the developer console now displays site-specific information about your app's invocation errors. Just select the invocation errors chart title, or select the More actions (⋯) menu on the chart and View details.

For more information, see Monitor your apps.

To help you monitor the performance of your Forge app, we’ve introduced alerts for when your app’s invocation success rate changes. If your app’s invocation success rate falls below 99%, we’ll send you an email. If you don’t want to receive these emails, you can mute and unmute the alert at any time.

To help you debug your Forge apps more easily, app logs are now available by default when a user installs your app on their site.

• Previously log access was disabled by default. If you needed log access for your app on a user’s site, you had to ask the user to manually give you log access through Admin Hub.

• Now log access is enabled by default. When a user installs your Forge app on their site, you will now have automatic access to logs for your app on their site.

Note, apps that are already installed will remain in their current state of log sharing, with log access disabled by default, but we are investigating how to change this.

Disabling access

Users can still manually disable or re-enable log access through Admin Hub. This will remove your access to the logs for your app on their site, including any historic logs that were generated when you previously had access.

To help you when handling logs for your Forge app, we have added new Logging guidelines for app developers. These guidelines outline some best practices to consider when handling logs and determining what data you should, and should not, be logging.

We recently launched a new developer support page, which serves as a centralized hub for reporting issues, managing your app and getting support. This page will streamline your experience of getting in contact with us for different areas of support:

• Bugs: Report development or Marketplace bugs

• Incidents: Report critical issues or breaking changes

• App listing: Edit your app or access Marketplace APIs

• Accounts and payment: Manage your Marketplace payments and licenses

• App migration: Get help with creating a cloud version of your app

• Security programs: Apply or adjust your program details

• Partner resources: Request access to exclusive partner content

• Ukraine support: Request emergency concessions or ask questions

If you have any questions, please get in touch with us via the developer community announcement.

In Jira expressions, you can now request the parent field for issues from company-managed projects. Previously, in Jira expressions, this functionality was only supported for subtasks from company-managed projects and issues from team-managed projects.

This change will be rolled out in August 2022 and will affect base-level issues (e.g. story, task) from company managed-projects. Additionally, in late 2022 or 2023, the parent field will start returning parents of epics in Jira expressions.

Note that the scope of this is Jira expressions only. We've already applied a similar change to the Jira REST API.

The custom field “Epic Name“ will become optional starting from 15 Jan 2023. It will remain available after that date, and no data will be lost.

To make it easier to track the performance of your shared apps, we’ve added quick-view cards on the developer console landing page, under a new ‘My shared apps’ section. These cards show your shared apps':

• Invocation success rate for the last 7 days

• Error count for the last 7 days

• Last deployment event

We deprecated AP.host.getSelectedText in Jira and Confluence on Jan 11, 2022, due to security and privacy concerns.

Removal of this API has begun and is rolling out across all cloud instances.

To cause minimum disruption, all calls to this API will now return an empty string ("").

For full details, see the CDAC post.

The contextId field in the extension context of the Custom field type module is deprecated and replaced with configurationId. The new field contains the same value as contextId previously did.

We’re changing this up to avoid confusion around the nomenclature contextId, which may be mistakenly interpreted as the ID of a field context. Instead, we’re referring to the ID of a field configuration here.

The contextId field will be removed on Nov 1, 2022.

Forge CLI now lints correct scope when Jira Software and Jira Service Management REST APIs are used.

The scope checks are based on the OpenAPI specifications:

• Jira Service Management: https://developer.atlassian.com/cloud/jira/service-desk/swagger.v3.json

• Jira Software: https://developer.atlassian.com/cloud/jira/software/swagger.v3.json

We have updated our security requirements for cloud applications, added new security requirements, and categorized requirements by app type and security requirement type. All cloud applications in the Atlassian Marketplace must adhere to the updated requirements by October 31, 2022.

Please see the blog post and FAQ page accompanying this announcement for more details, as well as this document for specific updates.