Skip to content
modsignal
Sign up

Atlassian (Jira)

atlassian.com · SaaS · watching since Aug 17, 2026 · RSS

Follow
https://developer.atlassian.com/cloud/jira/platform/changelog/Checked every 168 h · last checked 1 d ago · watching since Aug 17, 2026
Watch it yourself →

Current state

As of Aug 29, 2026

This changelog tracks Jira Cloud Platform API updates, deprecations, and feature additions for developers as of 28 August 2026. Recent highlights include a 10x increase in the Bulk fetch issues API limit (up to 1000 issues per request), beta support for global statuses in team-managed workflows, and the phased deprecation of Atlassian Analytics dashboard subscriptions. Multiple deprecation notices concern the workflowId field in Connect and workflow post function webhooks, with removal after 31 July 2027 in favor of workflowName/workflowEntityId.

Deprecations

  • workflowId field in webhook payloads sent to Connect workflow post functions

    → workflowName or workflowEntityId

    Sunset 2027-07-31

  • workflowId field in webhook payloads sent via the Trigger a webhook post function

    → workflowEntityId

    Sunset 2027-07-31

  • Dashboard subscriptions and server-side PDF/PNG exports in Atlassian Analytics

    Sunset 2026-11-02

  • Workflow transition properties APIs

    → Bulk get workflows and Bulk update workflows APIs

    Sunset 2026-07-13

  • Old workflow editor in Jira

    → new workflow editor

    Sunset 2026-07-13

Latest entries

    • Bulk fetch issues now supports up to 1000 issues per requestaddition
    • Global statuses are now available in team-managed workflowsaddition
    • Removing dashboard subscriptions and server-side PDF/PNG exports from Atlassian Analyticsdeprecation
    • Global status support announced for team-managed workflowschange
    • Deprecating workflowId in webhooks triggered from Connect workflow post functionsdeprecation
    • Deprecating workflowId in webhooks sent from the trigger a webhook workflow post functiondeprecation
    • Adding workflowEntityId in webhooks sent to Connect post functionsaddition
    • Added workflowEntityId field in webhooks triggered from workflow post functionsaddition
    • Removal of the workflow transition properties APIsbreaking
    • Forge custom field search aliases now support app-provided search suggestionsaddition
    • Connect EOS customer messaging to go live to production instances for select cohort of appschange
    • Support added for unlicensed, anonymous, and customer access for UIM Forge modulesaddition

Changes

  1. ChangeAPI changelog

    Bulk fetch issues API now supports up to 1000 issues per request (increased from 100), with specific requirements for field selection and restrictions on multi-value fields and certain expand parameters.

    Last updated Aug 26, 2026 CHANGELOG This page includes release notes and updates for Jira Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Jira Cloud Platform. Filter types 26 AUGUST 2026
    Last updated Aug 28, 2026 CHANGELOG This page includes release notes and updates for Jira Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Jira Cloud Platform. Filter types 28 AUGUST 2026 ADDED BULK FETCH ISSUES NOW SUPPORTS UP TO 1000 ISSUES PER REQUEST The Bulk fetch issues API (POST /rest/api/3/issue/bulkfetch) now supports a maximum of 1000 issues in a single request, up from the previous limit of 100. This higher limit is available for requests optimized for efficient processing. What's changing To qualify for the 1000-issue limit, your request must meet the following criteria: * Explicit field selection: You must explicitly name at least one field to include. Wildcards like *all or *navigable, and requests containing only exclusions (e.g., -description), are not eligible. * Field count: No more than 100 fields can be explicitly included. * Single-value fields only: Included fields must not return multiple values (e.g., comment, worklog, or attachment are excluded). * Restricted expands: The expand parameter must not include changelog, editmeta, operations, renderedFields, transitions, or versionedRepresentations.
    Confidence95%
  2. ChangeAPI changelog

    Removed section about Resource-Restricted Tokens for OAuth 2.0 (3LO) Apps; added new section about Global Statuses now available in team-managed workflows.

    ANNOUNCEMENT RESOURCE-RESTRICTED TOKENS FOR OAUTH 2.0 (3LO) APPS Resource-restricted tokens are now available for all developers creating new 3LO apps. When creating a new OAuth 2.0 (3LO) app via the Developer Console, you can now opt in to resource-restricted tokens. This ensures that access tokens issued for your app are scoped to only the specific Atlassian site a user explicitly selects during consent rather than granting broad access across all sites. MORE DETAILS The onboarding guide for Resource restricted apps is available here: https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/#oauth-2.0-(3lo)-apps
    26 AUGUST 2026 ADDED GLOBAL STATUSES ARE NOW AVAILABLE IN TEAM-MANAGED WORKFLOWS The Global Statuses Beta for team-managed spaces is now live. As previously announced, this feature allows global (site-wide) statuses to be added to team-managed workflows. To try it, enable the feature via Jira Labs. Once enabled: * Workflow create and update APIs support global statuses in team-managed workflows. * Space templates will create workflows with global statuses by default. * Global statuses may appear in workflow read responses for team-managed spaces.
    Confidence85%

This is the Product and API pack running on a real vendor.

Watch Atlassian (Jira) — or anything else — your way.

Your own prompt, cadence and channels. One alert with the before/after proof when your sentence comes true.

Get started