Wir prüfen täglich den Changelog und die OpenAPI-Spezifikation von Jira Cloud, weil wir produktive Integrationen auf der Jira Cloud API betreiben. Diese Seite listet die 93 Änderungen, die wir seit Beginn der Überwachung am 10. April 2026 erfasst haben, die neuesten zuerst.
Die Einträge geben die englischsprachigen Changelogs der Anbieter wieder und stehen deshalb auf Englisch.
Die letzte erfolgreiche Prüfung war am 28. September 2026. Wir kümmern uns darum; bis dahin fehlen hier eventuell die neuesten Änderungen.
2 Breaking Changes und 11 Deprecations in der Jira Cloud API in den letzten 90 Tagen. Zuletzt: „Deprecation of legacy Jira dashboard Forge modules“ (23. September 2026).
Letzte Erkennung, 8. Oktober 2026 The `/rest/api/3/label` endpoint now accepts optional `query` and `scope` request parameters. No changes are required unless you want to use them.
Die Einordnung erfolgt automatisch. Prüfen Sie die Notiz des Anbieters, bevor Sie Aufwand einplanen.
jira:dashboardGadget and jira:dashboardBackgroundScript modules are deprecated in favor of new dashboards:widget and dashboards:backgroundScript modules, with removal on May 17, 2027.
Betrifft das eine Ihrer Integrationen? Wir übernehmen die Umstellung zum Festpreisdashboards:widget and dashboards:backgroundScript Forge modules are now GA for building extensions on the upgraded Jira dashboard experience rolling out September 23, 2026.
Internal improvement to Forge permission checks for asApp requests that removes requirement for permissions to be synced at installation time; no action required.
New POST /rest/api/3/workflows/copy endpoint added to copy existing workflows programmatically via REST API, previously only available through UI.
Conditional execution for Jira workflow post functions: New RFC proposal for conditional execution capability in Jira workflow post functions, open for community feedback.
New asynchronous bulk mutation APIs for Jira Cloud REST API: RFC proposing new asynchronous bulk mutation APIs for large-scale data operations with job tracking and status polling, open for community feedback.
Detail view in List and Global Search views is being deprecated in favor of resizable preview panels or modals for opening work items.
Issue and project context is now available in extension context during issue-bulk-edit rendering, removing previous limitation that required fallback UI.
Bulk fetch issues API (POST /rest/api/3/issue/bulkfetch) increased limit from 100 to 1000 issues per request with specific criteria for explicit field selection and single-value fields only.
Global (site-wide) statuses are now live in team-managed workflows, with workflow create/update APIs supporting global statuses and space templates creating workflows with them by default.
Dashboard subscriptions on Atlassian Analytics are being deprecated in stages: creation disabled September 8, 2026; full removal November 2, 2026.
Dashboard subscriptions and server-side PDF/PNG exports from Atlassian Analytics: Dashboard subscriptions are being deprecated starting September 2026, with full removal by November 2, 2026.
Removing dashboard subscriptions and server-side PDF/PNG exports: Dashboard subscriptions in Atlassian Analytics are being phased out, with creation disabled September 8, 2026 and full removal November 2, 2026; integrations relying on emailed dashboard reports must migrate to alternatives.
Dashboard subscriptions are being deprecated with creation blocked September 8, 2026 and full removal for low-touch customers by November 2, 2026.
The Forge bridge invoke method now accepts an optional metadata argument to return additional information like rate limiting details alongside the response.
Global status support in team-managed workflows: Beta feature enabling global (site-wide) statuses in team-managed workflows with API support for workflow create/update operations; feature is opt-in via Jira Labs with no breaking changes to API shapes.
Team-managed workflows now support global (site-wide) statuses through updated workflow create/update APIs, with API shapes remaining unchanged and feature opt-in via Jira Labs.
workflowEntityId in workflow post function webhooks: New workflowEntityId field added to webhook payloads from workflow post functions, enabling proper workflow operations via REST APIs.
The workflowEntityId field has been added to webhook payloads sent to Connect applications for workflow post function triggers, enabling proper workflow identification via REST APIs.
New workflowEntityId field added to webhook payloads sent to Connect Post Functions to enable proper workflow identification and querying via Workflow REST APIs.
The workflowId field in webhooks from Connect workflow post functions is deprecated and returns a placeholder value; will be removed after July 31, 2027; should be replaced with workflowName or workflowEntityId.
workflowId field in Trigger a webhook post function webhook payloads is deprecated and returns placeholder value, will be removed after July 31, 2027; use workflowEntityId instead.
Betrifft das eine Ihrer Integrationen? Wir übernehmen die Umstellung zum FestpreisworkflowId field in Connect workflow post function webhook payloads is deprecated and returns placeholder value, will be removed after July 31, 2027; use workflowName or workflowEntityId instead.
Betrifft das eine Ihrer Integrationen? Wir übernehmen die Umstellung zum FestpreisworkflowId field in Connect workflow Post Function webhooks: The workflowId field in webhook payloads sent to Connect workflow Post Functions is being deprecated and will be removed after July 31, 2027, replaced by workflowName or workflowEntityId.
Removal of Workflow transition properties APIs: The Workflow transition properties APIs have been removed from the public API; integrations must migrate to Bulk get workflows and Bulk update workflows APIs.
Forge apps can now provide custom search suggestions for searchAlias properties of Forge object custom fields by setting searchSuggestionsEnabled: true.
Workflow transition properties APIs have been removed from public API; integrations must migrate to Bulk get workflows and Bulk update workflows APIs.
Connect EOS customer messaging rollout to production: Admin-facing migration messaging on Connected Apps page will roll out to production instances in approximately two weeks for select app cohorts; apps must adopt connectToForgeMigration module and declare migration intent.
Admin-facing migration messaging for Connect apps will roll out to production instances starting approximately two weeks after July 9; apps must adopt connectToForgeMigration module and declare migration intent.
Admin-facing migration messaging for Connect apps will roll out to production instances in approximately two weeks for apps without Forge adoption or marked as migration intent 'no' or 'unsure'.
Admin-facing migration messaging for Connect apps rolling out to production instances starting mid-July 2026 for select cohorts based on connectToForgeMigration declaration.
Support for Unlicensed/Anonymous/Customer Access for UIM Forge Modules: jira:uiModifications module now supports configuration for anonymous, unlicensed, and customer user types via unlicensedAccess property in manifest.
UI Modifications modules can now explicitly declare support for anonymous, unlicensed, and customer users via the unlicensedAccess property to avoid being blocked after June 29, 2026.
Forge UI Modifications modules can now explicitly declare support for anonymous, unlicensed, and customer users via the unlicensedAccess property in the manifest.
Status Search API now supports filtering by global statuses: Status Search API now supports includeGlobalStatuses query parameter to include global statuses alongside project-specific statuses in responses.
New optional includeGlobalStatuses query parameter added to Status Search API to include global statuses in project-scoped queries.
Removal of old workflow editor: Access to the old workflow editor will be removed for all customers starting July 13, 2026; workflow-related apps should ensure compatibility with the new editor.
Removal of old workflow editor: Access to old workflow editor will be completely removed starting July 13, 2026; workflow apps should be tested in new editor and rule descriptions implemented.
Removal of the old workflow editor in Jira: Access to the old workflow editor will be removed for all customers starting July 13, 2026; apps should ensure compatibility with the new editor.
Workflow Search API now supports optional projectId query parameter to filter workflows used by a specific project.
The Workflow Search API now supports an optional projectId query parameter to filter workflows used by a specific project.
New structured process for investigating security incidents with log sharing for Forge apps and single reporting path via developer support portal.
Resource-restricted tokens are now available for new 3LO apps, scoping access tokens to specific Atlassian sites rather than granting broad access.
Update Jira UI Modifications manifest for anonymous user support: jira:uiModifications modules must declare unlicensedAccess attribute to support anonymous users; change takes effect June 29, 2026.
Update Jira UI Modifications manifest for anonymous user support: UI Modifications apps must explicitly declare unlicensedAccess: [anonymous] in manifest by June 29, 2026 or will stop executing for anonymous users.
Guest access now supported for jira:customField, jira:customFieldType, and jira:issuePanel modules through the unlicensedAccess property.
New unlicensedAccess property added to jira:customField, jira:customFieldType, and jira:issuePanel modules to enable guest and unlicensed user access.
Apps with UI Modifications that need to work for anonymous users must explicitly declare support using unlicensedAccess attribute; change takes effect June 29, 2026; modules will not execute for anonymous users without explicit declaration.
Forge triggers can now filter events using Jira entity properties and include enriched payload data, reducing unnecessary executions.
New AI chat widget added to developer.atlassian.com for logged-in users to answer questions and surface relevant documentation.
Forge custom fields now appear as selectable columns in Jira's List View with formatter support, though inline editing is not available.
Forge UI Modifications configured for Issue View now apply when issues are opened via ViewIssueModal, requiring no code changes.
Consolidated security compliance expectations document published covering vulnerability management, OAuth compliance, partner verification, and incident response.
A new consolidated Marketplace Security Enforcement Policy has been published covering vulnerability management, OAuth compliance, and incident response expectations.
Shortened remediation timelines for critical (10 days), high (4 weeks), medium (12 weeks), and low (25 weeks) vulnerabilities in Marketplace cloud apps, effective September 1, 2026.
Updated cloud app SLOs and new enforcement policy: Marketplace cloud app vulnerability remediation SLOs are shortened (Critical: 10 days, High: 4 weeks, Medium: 12 weeks, Low: 25 weeks), effective September 1, 2026, with a new Marketplace Security Enforcement Policy published.
JQL functions membersOf(), aqlFunction(), and organizationMembers() that exceed 10,000 items will return errors; comments, worklogs, and history searches will only cover the most recent 1,000 items per issue effective August 18, 2026.
JQL queries using membersof() and aqlFunction() exceeding 10,000 items will error; searches for comments, worklogs, and issue history limited to most recent 1,000 items per issue effective August 18, 2026.
JQL functions membersOf(), aqlFunction(), and organizationMembers() limited to 10,000 results; comments/worklogs/history limited to 1,000 items per issue; effective August 18, 2026.
New Tile component added to Forge UI Kit for displaying assets like emojis with customizable sizes, colors, borders, and padding.
Two REST API v2 endpoints for updating custom fields now support an optional `generateAppEvents` parameter to suppress app event generation when set to false.
Action validator jira:actionValidator now supports workItemTypeChanged across multiple flows (issue view, move, bulk move, convert subtask) and adds new context variable newIssueTypeData for more refined conditions.
workItemTypeChanged validator now supports issue view, move issue, bulk move, and convert operations; new newIssueTypeData context variable added.
New additionalDetails field added to validate create and update workflow API responses to provide additional context for validation warnings and errors.
Breaking change removing support for permission grants using non-group-picker custom fields; effective May 12, 2026.
Boolean usages of autoFocus prop removed from @atlaskit/modal-dialog; focus now automatically moves to first interactive element with no option to disable.
jira:issueGlance module is being deprecated in favor of jira:issueContext module and will be removed from work items.
jira:customField, jira:customFieldType, and jira:issuePanel modules now support unlicensed and anonymous users via new unlicensedAccess property in manifest.yml.
Classic API tokens deprecated for JPD GraphQL queries effective November 1, 2026; fine-grained scoped tokens required, with some queries no longer supporting API tokens.
Development ceased April 30, 2026; limited vulnerability patching continues until Q4 2026 when Connect enters final EOS; frameworks available as open-source under Apache 2.0.
Jira Cloud now strictly enforces valid JQL syntax effective June 11, 2026; invalid clauses or unsupported operators will return zero results instead of being handled leniently.
Invalid JQL syntax and unsupported operators now return zero results instead of partial matches; change takes effect June 11, 2026.
Jira Cloud now strictly enforces valid JQL syntax and operators; previously tolerated invalid clauses now return zero results, aligning with Data Center behavior and creating non-backward-compatible changes, effective June 11, 2026.
Draft workflow parameters will be removed from workflow transition rule APIs on November 2, 2026; requests using draft flag will return HTTP 400.
AUI CDN (aui-cdn.atlassian.com) will be shut down after Oct 30, 2026; apps must migrate to Atlassian Design System, Forge UI Kit, or self-host AUI assets.
The spacing prop on icon components in @atlaskit/icon and @atlaskit/icon-lab is deprecated and will be removed in a future major release; developers should use Flex wrapper with explicit padding tokens instead.
Legacy icon entry points (glyph, core/migration, utility, base, svg, migration-map) permanently removed from @atlaskit/icon; must use @atlaskit/icon/core instead.
The Create workflow API has been removed and calls now result in 404 Not Found errors; developers should use Bulk create workflows or Bulk update workflows instead.
The Get all workflows API has been removed from the public API as of April 2, 2026; developers should use the Search workflows API instead.
Forge modules (customField, customFieldType, issuePanel) now support anonymous and unlicensed users via new unlicensedAccess property, enabling apps to work on publicly accessible pages.
Managing limitations in custom JQL functions: Published a new guide covering four practical strategies for handling custom JQL functions that return more than 1,000 values.
Connect private apps can no longer be installed; partners cannot update Connect apps via descriptors; private apps must now be distributed via Forge installation links.
Forge apps with app.connect.key in manifest can now retrieve the Connect clientKey via a reserved read-only app property to facilitate migration from Connect.
Custom JQL function errors are now classified as JQL validation errors and displayed inline with custom error messages shown directly to end users.
OAuth 2.0 apps now support multiple admins assignment and ownership transfer in the developer console.
jira:globalBackgroundScript module now supports experience-based access control, modal support, and view context access (issueKey, projectId, boardId, project.type).
New asynchronous bulk API allows Jira administrators to pin or unpin Forge issue panels to up to 1,000 projects in a single request.
Platform-level URL persistence and redirect feature enables legacy Connect URLs (including path, query parameters, and fragments) to transparently redirect to corresponding Forge app modules.
Issue Action, Issue Activity, Issue Panel, Issue Context, Custom Field, Custom Field Type, JQL Function, and Entity Property modules are now available as dynamic modules in Forge Early Access Program.
Custom field context default value REST APIs: Existing APIs for managing context default values are deprecated (July 2026) and removed (October 2026) to support multiple default values per context; new APIs will be introduced.
Developers can now nominate genuine migration blockers or major customer-impact risks for Forge migration review via the Request review flow on FRGE before Connect end of support in December 2026.
As of March 2, 2026, phased enforcement of points-based quota rate limits has begun with rollout to a small percentage of apps gradually expanding; all Forge, Connect, and OAuth 2.0 apps affected with new Beta-prefixed rate limit headers.
The Connect Inspector Service has been decommissioned as of March 1, 2026; an open-sourced version is available for developers needing similar functionality.
Unterschiede zwischen aufeinanderfolgenden Versionen der veröffentlichten OpenAPI-Spezifikation von Jira Cloud, ermittelt mit oasdiff. Aufgeführt sind nur Änderungen, die bestehende Clients brechen oder brechen können.
GET /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'dashboards/items/editPermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'dashboards/items/editPermissions/items/project/allOf[#/components/schemas/Project]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'dashboards/items/editPermissions/items/role/allOf[#/components/schemas/ProjectRole]/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'dashboards/items/sharePermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'dashboards/items/sharePermissions/items/project/allOf[#/components/schemas/Project]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'dashboards/items/sharePermissions/items/role/allOf[#/components/schemas/ProjectRole]/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' POST /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'editPermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' POST /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'editPermissions/items/project/allOf[#/components/schemas/Project]/projectTypeKey' response property for the response status '200' POST /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'editPermissions/items/role/allOf[#/components/schemas/ProjectRole]/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' POST /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'sharePermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' POST /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'sharePermissions/items/project/allOf[#/components/schemas/Project]/projectTypeKey' response property for the response status '200' POST /rest/api/3/dashboard added the new 'product_discovery' enum value to the 'sharePermissions/items/role/allOf[#/components/schemas/ProjectRole]/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/search added the new 'product_discovery' enum value to the 'values/items/editPermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/search added the new 'product_discovery' enum value to the 'values/items/editPermissions/items/project/allOf[#/components/schemas/Project]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/search added the new 'product_discovery' enum value to the 'values/items/editPermissions/items/role/allOf[#/components/schemas/ProjectRole]/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/search added the new 'product_discovery' enum value to the 'values/items/sharePermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/search added the new 'product_discovery' enum value to the 'values/items/sharePermissions/items/project/allOf[#/components/schemas/Project]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/search added the new 'product_discovery' enum value to the 'values/items/sharePermissions/items/role/allOf[#/components/schemas/ProjectRole]/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/{id} added the new 'product_discovery' enum value to the 'editPermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/{id} added the new 'product_discovery' enum value to the 'editPermissions/items/project/allOf[#/components/schemas/Project]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/{id} added the new 'product_discovery' enum value to the 'editPermissions/items/role/allOf[#/components/schemas/ProjectRole]/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/{id} added the new 'product_discovery' enum value to the 'sharePermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/{id} added the new 'product_discovery' enum value to the 'sharePermissions/items/project/allOf[#/components/schemas/Project]/projectTypeKey' response property for the response status '200' GET /rest/api/3/dashboard/{id} added the new 'product_discovery' enum value to the 'sharePermissions/items/role/allOf[#/components/schemas/ProjectRole]/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' PUT /rest/api/3/dashboard/{id} added the new 'product_discovery' enum value to the 'editPermissions/items/project/allOf[#/components/schemas/Project]/issueTypes/items/scope/allOf[#/components/schemas/Scope]/project/allOf[#/components/schemas/ProjectDetails]/projectTypeKey' response property for the response status '200' GET /rest/api/3/uiModifications added the new 'GICAgentView' enum value to the 'values/items/contexts/items/viewType' response property for the response status '200' GET /rest/api/3/uiModifications added the new 'IssueTransitionAgentView' enum value to the 'values/items/contexts/items/viewType' response property for the response status '200' GET /rest/api/3/uiModifications added the new 'IssueViewAgentView' enum value to the 'values/items/contexts/items/viewType' response property for the response status '200' POST /rest/api/3/project removed the enum value 'com.atlassian.servicedesk:next-gen-general-service-desk' of the request property 'projectTemplateKey' GET /rest/api/3/project/{projectIdOrKey}/roledetails added the new 'AI_AGENT_ROLE' enum value to the '/items/type' response property for the response status '200' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueDateTime]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueDate]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueFloat]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueForgeMultiStringField]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueForgeObjectField]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueLabels]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueMultipleVersionPicker]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueReadOnly]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueSingleVersionPicker]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueTextArea]/contextId' PUT /rest/api/3/field/{fieldId}/context/defaultValue added the new required request property 'defaultValues/items/oneOf[#/components/schemas/CustomFieldContextDefaultValueTextField]/contextId' GET /rest/api/3/workflow/rule/config the response property 'values/items/workflowId/draft' became optional for the status '200' PUT /rest/api/3/workflow/rule/config the response property 'updateResults/items/workflowId/draft' became optional for the status '200' PUT /rest/api/3/workflow/rule/config/delete the response property 'updateResults/items/workflowId/draft' became optional for the status '200' POST /rest/atlassian-connect/1/migration/workflow/rule/search the response property 'validRules/items/workflowId/draft' became optional for the status '200' POST /rest/api/3/project removed the enum value 'com.atlassian.servicedesk:simplified-general-service-desk' of the request property 'projectTemplateKey' Wir beobachten Jira Cloud, weil wir Integrationen darauf betreiben. Hängt eine Ihrer Integrationen an Jira Cloud, übernehmen wir sie: sauber gebaut, dauerhaft betrieben und angepasst, wenn Jira Cloud etwas ändert, bevor Ihre Daten betroffen sind. Festpreisangebot innerhalb von 48 Stunden.