-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
-
Confluence
This request originates from a highly engaged and frustrated customer who has experienced multiple brief but impactful service disruptions that were not reflected on `status.atlassian.com`.
The customer's primary concern is the lack of transparency regarding incidents that affect their environment but are not considered widespread enough to be publicly announced. This has caused significant business disruption, internal confusion, and a loss of trust.
The customer understands that not all incidents are public, but they believe the internal criteria and policy for this non-disclosure should be made public. They argue that this is a fundamental policy issue, not a simple feature request.
Specific requests from the customer:
- Policy Disclosure: Provide a public URL or documentation that explains the internal policy on why certain incidents are not publicly disclosed. They specifically cite the incident in ticket `JPNS-98997` as an example of an event that affected their business but had no public record.
- Proactive Notification: Customers want a way to be notified of temporary or minor incidents that directly affect their site, even if these incidents do not meet the criteria for public status page publication.
- Process for Policy Change: Clarify the official process for customers to request a change to this incident communication policy. The existing ticket CLOUD-11407, which focuses on "clarifying criteria," is seen as insufficient for their request for a policy change.
Expected Outcome:
- Public documentation outlining the policy on incident communication and disclosure.
- A mechanism to alert affected customers of minor, site-specific incidents.
- A clear path for customers to formally request changes to these policies.
Impact:
- Customer Trust: Resolving this issue will significantly improve customer trust and satisfaction.
- Operational Efficiency: Customers can quickly distinguish between their own configuration issues and Atlassian-side incidents, reducing time spent on unnecessary troubleshooting.
- Business Continuity: Improved communication about minor incidents helps customers maintain business continuity and avoid business losses due to service disruptions.