Incident Communication in JSM
 Rate how relevant the below capabilities will be to you if they are added to JSM
Sign in to Google to save your progress. Learn more
Are you an Atlassian employee *
Automatic connection from JSM to Statuspage on a major incident or preconfigured trigger
Not relevant
Extremely relevant
Clear selection
3rd party automation - in addition to connection to Statuspage, connecting the incident update comms to other tools like Pagerduty
Clear selection
Informing users about change management initiatives which may disrupt their services
Not relevant
Extremely relevant
Clear selection
Automatic Downstream and upstream updates - identifying dependencies between own and 3rd party services and displaying relevant status based on that
Not relevant
Extremely relevant
Clear selection
Proactive possible incident communication before the incident has occurred
Not relevant
Extremely relevant
Clear selection
2- way communication/ feedback mechanism
Not relevant
Extremely relevant
Clear selection
Chatops integration
Not relevant
Extremely relevant
Clear selection
SEO optimization for Statuspage/native site
Not relevant
Extremely relevant
Clear selection
Incident communication insights and reporting
Not relevant
Extremely relevant
Clear selection
Historical Uptime and Performance display
Not relevant
Extremely relevant
Clear selection
Notification redundancy - Connecting to many notification services in-order to ensure high deliverability
Not relevant
Extremely relevant
Clear selection
Intelligent communication plan templates defining the language, frequency and possible contact/subscribers/stakeholder list and app to send the communication to
Not relevant
Extremely relevant
Clear selection
Please share any other pain-point/feature request you have wrt stakeholder communications during incident management. Contact rsrivastava@atlassian.com for any more comments.
Submit
Clear form
Never submit passwords through Google Forms.
This form was created inside of Atlassian. Report Abuse