This issue must be prioritized, as the lack of this functionality is having a significant impact on our daily operations. Advance notice of maintenance would allow us to plan our activities effectively.

Honestly, I think that this feature should already be native for a suite of tools like Atlassian provide to its customers. Because for people like me, working as platform supervisors, having a preemptive notification that a feature release could cause downtime (and a subsequent contingency plan, by following ITIL practices), it's a life saving opportunity, therefore avoiding a big blind spot in our monitoring capabilities.

Please move it forward as fast as you can.

I believe this situation needs immediate attention. It’s not feasible to wait for thousands of users to upvote a feature request that should already be implemented. (We are talking about just sending a notification when you know something will probably happen).

As a result, the absence of this functionality is impacting our reputation with customers. As we are paying for a service, we expect it to meet our needs, and therefore, I kindly request that you expedite the rollout of this feature, as it seems to me that it should already be a standard offering.

We experienced an unexpected Jira Service Desk outage causing disruption to our business. While the service was restored sooner than the projected 2-hour maintenance window, we were not notified of this planned downtime. This prevented our clients from raising support tickets and hindered our team's communication.

To avoid future disruptions, we request maintenance notifications. Receiving timely email alerts about planned Jira Service Desk maintenance will allow us to proactively inform our clients and implement contingency plans to ensure uninterrupted support.