A new Rovo-powered AI chat widget is now available for all logged-in users on https://developer.atlassian.com. Located in the bottom right corner of developer documentation pages, this assistant can answer questions, surface relevant docs, and help you build on the platform faster.

Key features include:

• Contextual answers: The chat understands the context of your question and provides relevant answers rather than generic search results.

• Developer-focused knowledge: Trained on Atlassian developer documentation, the assistant understands Forge, REST APIs, Marketplace, and platform concepts.

• Natural language understanding: Ask questions in plain language; no need to know exact documentation titles or keywords.

• Follow-up questions: Continue a conversation naturally with follow-up questions to drill deeper into a topic.

• Source transparency: The widget displays the specific documentation and support sources used to generate each answer.

• Conversation history: You can access and review your previous interactions for up to 28 days.

• Independent operation: The assistant works independently of your product licenses and organization-level AI settings.

For more details on how the assistant handles data and what sources it uses, see the Atlassian developer AI chat documentation.

You can now use Jira entity properties (issue, project, and user) to filter Forge trigger events and include them in the delivered event payload. This allows your app to process only relevant changes and reduces unnecessary executions.

What’s changing

• Entity property filtering: You can now define expressions in your manifest.yml that use Jira entity properties to filter events before they trigger your app.

• Payload enrichment: Relevant entity properties can now be included directly in the event payload, eliminating the need for additional REST API calls to fetch this data.

What you need to do

• Update your manifest.yml to include expression filters using entity properties.

• Update your event handlers to utilize the enriched payload data.

• For more information, see the Forge Trigger module reference.

Forge custom fields and Forge custom field types are now displayed as columns in Jira's https://support.atlassian.com/jira-software-cloud/docs/what-is-the-list-view/ (New Issue Navigator).

What's new:

• Forge custom fields appear as selectable columns in the List View.

• When a formatter is defined in your manifest, the List View evaluates and displays the formatted value instead of the raw stored value.

Limitations:

• Read-only — Inline editing of Forge custom field values is not available in the List View. Users must open the issue to edit.

• No Custom UI / UI Kit rendering — The view.resource component is not rendered; field values are displayed as text only.

Read more here :

• https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#list-view

• https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field-type/#list-view

Forge apps using the UI Modifications API configured for Issue View will now have their modifications applied when issues are opened via ViewIssueModal (for example, from global pages, admin pages, or custom UI panels).

Previously, UI Modifications were not loaded silently in this context. This applies to all supported project types, and requires no changes to your app's manifest or code

For more details, see the Jira UI modifications documentation.

As recently announced in Raising the bar on Marketplace cloud app security: together we are updating the Marketplace Security Bug Fix Policy to shorten vulnerability remediation timelines for Marketplace cloud apps. These changes ensure a higher security standard across our ecosystem.

What’s changing
The remediation Service Level Objectives (SLOs) for Marketplace cloud apps are being shortened. The timelines for Data Center apps remain unchanged.

Updated Cloud App SLOs (Enforceable September 1, 2026):

• Critical: 10 days

• High: 4 weeks

• Medium: 12 weeks

• Low: 25 weeks

Data Center App SLOs (Unchanged):

• Critical: 12 weeks

• High: 12 weeks

• Medium: 12 weeks

• Low: 25 weeks

Additionally, we have published the Marketplace Security Enforcement Policy, a consolidated source of truth for marketplace security compliance expectations, including vulnerability management, OAuth compliance, partner verification, bug bounty participation, and incident response.

What you need to do

• Review the new timelines: Ensure your internal processes are updated to meet the new cloud app SLOs by September 1, 2026.

• Check your tickets: We have corrected an issue where some AMS Data Center tickets incorrectly showed cloud remediation dates. If you believe a ticket still has an incorrect date, please raise an ECOHELP ticket.

• Watch the policy page: The Marketplace Security Enforcement Policy is a living document, we recommend "watching" the page for future updates.

We are adjusting how some JQL features behave to keep search fast and reliable. Queries using functions membersof() and aqlFunction() that expand to very large sets will return an error identifying the clause to adjust. For comments, worklogs, and issue history (searches using operators WAS or CHANGED), JQL searches cover only the most recent entries per issue.

Jira data and permissions are unchanged.

Effective date: Aug 18, 2026

We've introduced the Tile component for Forge UI Kit apps, now available in Preview. The Tile component is a rounded square container for displaying assets like emojis, or objects in a consistent, styled way.

The component supports various sizes (from 16px to 48px), customizable background colors using design tokens, optional borders, and adjustable internal padding for different asset types including third-party logos.

For implementation details and examples, see the Tile component documentation.

A new optional boolean parameter, generateAppEvents has been introduced to the following Jira Cloud REST API endpoints

• POST /rest/api/2/app/field/value - Update custom fields

• PUT /rest/api/2/app/field/{fieldIdOrKey}/value - Update custom field value

What it does: When set to false, this parameter suppresses the generation of app events triggered by the update. Specifically, it prevents issue updated events from being dispatched to:

• Forge app event listeners

• Connect app event listeners

• OAuth 2.0 app webhooks

• Admin-configured webhooks (registered via the Jira admin UI)

Default behavior: When omitted or set to true, all app events are generated as usual.

The jira:actionValidator module (Preview) now supports the workItemTypeChanged action across multiple flows, enabling custom validation whenever a user changes a work item's type. The validator is triggered in:

• Issue view - the user changes the work item type from the type field on the issue view.

• Move issue - when the work item type changes as part of moving an issue.

• Bulk move/migrate - the work item type changes as part of a bulk move or migration.

• Convert to subtask - when a standard work item is converted to a subtask type.

• Convert subtask to a work item - when a subtask is converted to a standard work item.

Also, a new context variable newIssueTypeData (type: IssueType) has been onboarded alongside the existing newIssueType (type: String, returns the issue type ID), allowing more refined conditions on the target work item type within your Jira expression.

Read more here - https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-action-validator/#workitemtypechanged

We’ve added a new field additionalDetails to the response object for the validate update workflows and validate create workflows APIs.

This will contain additional context if applicable related to the validation warnings and errors returned from the APIs.

We are removing support in Jira for permission grants that rely on certain non–group-picker custom fields. These grants work by matching a field's selected option name to a group name; a pattern that is being deprecated in favor of explicit group‑picker fields.

Effective date: May 12, 2026

Affected custom field types:

• com.atlassian.jira.plugin.system.customfieldtypes:select

• com.atlassian.jira.plugin.system.customfieldtypes:multiselect

• com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons

• com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes

• com.atlassian.jira.plugin.system.customfieldtypes:datetime

• com.atlassian.jira.plugin.system.customfieldtypes:textfield

• com.atlassian.jira.plugin.system.customfieldtypes:jwm-category

• com.pyxis.greenhopper.jira:gh-epic-status

What happens after this date:
Permission grants that reference the above field types will no longer be evaluated. Affected issues may lose their expected access grants.

What you should do:

• Review your permission schemes for grants that use these field types and replace them with explicit group-picker fields. See What are permission schemes in Jira? | Atlassian Support for guidance.

• To identify affected schemes, go to Jira administration → Permission schemes and check for grants tied to the field types listed above.

The boolean usages of the autoFocus prop have now been removed from @atlaskit/modal-dialog. The previously default value of true, which automatically moves focus to the first interactive element within the modal, is now the default with no option to set it to false. This is to improve accessibility and follow the WCAG guidelines for focus within a modal dialog.

Boolean usages of autoFocus can be removed by running the included codemod.

We are announcing the deprecation of https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-glance/ (jira:issueGlance), as we have replaced with https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-context/ (jira:issueContext) module. The Jira Issue Glance module will soon be removed from the work items completely.

Please refer to the following documentation for more details - https://developer.atlassian.com/cloud/jira/platform/future-proof-issue-glance-implementation/

Following Forge modules - jira:customField, jira:customFieldType and jira:issuePanel can now run for unlicensed and anonymous users in Jira and Jira Service Management. This means your apps will work on publicly accessible pages and for users who don't have a full Jira and JSM license.

By default, Forge apps only run for licensed Jira and JSM users. To allow your app to serve unlicensed and anonymous users, add the unlicensedAccess property to your modules in manifest.yml.

Please refer to following guide for more details - https://developer.atlassian.com/platform/forge/access-to-forge-apps-for-unlicensed-users/#introduction.

We’r’e deprecating support for classic (unscoped) API tokens in Jira Product Discovery (JPD) GraphQL queries. In addition, some GraphQL queries will no longer be accessible via API tokens.

What's changing: Starting Nov 1, 2026, all JPD GraphQL query operations currently accessible via classic API tokens will require fine-grained scoped tokens instead. After this date, requests using classic tokens will be rejected with an authentication error.

What you need to do:

1. Create a new fine-grained API token in your Atlassian account settings.

2. Select the JPD scopes your integration requires.

3. Update your integration to use the new token.

4. Retire your old classic token.

Reference: For more information, see: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Deprecation-of-classic-API-token-access-for-Jira-Product/ba-p/3228037