Freshservice approval groups and chains
First check whether custom approvals need an extension. Freshworks has separate migration windows for Pro and Enterprise customers whose workflows passed its impact scan.
The service desk. Right now.
Look up changes to service-desk platforms. Each entry identifies the rollout or support date and what a service owner should check.
End-of-November cutoff to contact Freshworks after reviewing a workflow for the extension list.
The Pro batch runs December 1–9 for customers with no detected impact.
Atlassian lists this as the end of support for the 10.3 LTS branch.
The Enterprise batch runs December 10–17 for customers with no detected impact.
Portal request-form customizations stop running if the app lacks a complete required permission set.
Atlassian plans to begin using the additional ranges.
Freshworks schedules the final transition for remaining customers.
Atlassian schedules the purchase cutoff for existing customers buying new subscriptions, apps or expansions.
Atlassian schedules the end of life for Jira Service Management Data Center.
6 records
First check whether custom approvals need an extension. Freshworks has separate migration windows for Pro and Enterprise customers whose workflows passed its impact scan.
The long-term-support window for this release closes in December. Identify sites on 10.3 before choosing the next supported branch.
Forge apps that customize portal request forms need a service-management permission set by the enforcement date.
Service teams with manually maintained network allowlists have a dated change for Jira Cloud API and webhook connections.
Build a migration plan around the subscription milestones as well as the end date for the installed product.
Simplified ITSM 3.2.3 groups multi-item order-guide approvals and email at the parent request level. Validate an existing guide through submission and approval.
No matching records. Try another filter or search term.