-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
Hi
To keep a long story short. What we lack is a proper way to handle incidents and the communication part with customers.
1. an incident (Jira issue) need a connection to multiple (affected customers). we solved this by adding customers as objects in Insight and then add customers to the incident ticket which is not ideal when we have the customers already in SD. To add on that, the customer in SD is not necessarily the right contact for incidents so that needs to be handled in another way.
2. it should be possible to have different customer incident data for the same incident without having to create subtasks or similar. For instance, downtime can differ from customer to customer. With over 200 customer I dont want to have 200 subtasks. but I still want to be able to add downtime/uptime info for each customer.
3. a neat way to communicate with the customers (incident contacts). I want to be able to send updates about the incident, containing incident information and also unique data like the downtime/uptime to assigned incident contacts with a preview functionality so that IMs can view and verify the mail going out before it reaches the customer.
Today im trying to solve this with Insight plugin to keep all customer organizations and their insight contacts as objects and hten use a script so find all selected affected customers, find the contacts email and generate an email. This is quite heavy stuff. And still I dont know how to solve the problem with keeping only the incident ticket but different customer data without subtasks. i think ServiceNow can do this.
thanks you
- relates to
-
JSDSERVER-14739 Add an option to avoid agents creating duplicate tickets for same incident
- Gathering Interest
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Jira Service Management, Server & Data Center