Comments
-
Hi @Evania Zhang , Thank you for the clarification and the correction! We appreciate the guidance. We understand now — promotional content about apps should be posted in App Central or Atlassian Solution Partners groups, not in the main Q&A categories. We'll repost our launch announcement in the appropriate channel. We…
-
Hi @Jean Horn , Thank you for the warm welcome and guidance! 🙏 You're absolutely right — we want to do this the right way. We've been answering SLA questions authentically in the community (like Donna's thread), and we appreciate the reminder about engagement guidelines. We'll check out the partner rules and make sure…
-
Great move by Atlassian! Customers definitely need clarity on their SLA status. This makes the internal side even more critical though — your team needs real-time visibility to actually meet those customer expectations before they go public. The gap we see teams hit: ✓ Customers see their SLA status (Atlassian's portal) ✗…
-
Absolutely! For exactly what you need — real-time visibility into SLA trigger events and which fields are satisfying (or failing) your SLAs — here are the key capabilities to look for: Real-time SLA Status Dashboard — See at a glance which tickets are On Track, At Risk, or Breached Trigger Event Audit Trail — Exact…
-
Hi Donna, Great follow-up data — the issue history is actually revealing something the others haven't flagged yet. Looking at your timestamp data more carefully: Incident #1: Created: Aug 11, 5:34 PM (outside business hours ✓) First "Date of Last Comment to Customer": Aug 12, 12:43 PM But actual "Responded" field marked:…
