Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5302

Service Desk customer notification audit

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Email - Outgoing
    • None
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Background and reason for this suggestion

      Currently, JIRA Service Desk provides a history for incoming emails processed but it doesn't show the history of generated customer notifications.

      Up until now, I have encountered two bugs which caused Service Desk customer notifications not going out. These were JRASERVER-64325 and JSDSERVER-5273.

      To prevent them to happen I have created a non-JIRA dashboard which queries the database directly and shows me troublesome database entries. This is sufficient for issues I am aware of, but if any new type of problem occurs, I will not notice it until my customers report it to me.

      The essence of this suggestion

      I propose a _ new feature of _JIRA Service Desk customer notification audit,  where admins could see the frequency of outgoing customer emails and maybe even, set alarm rules for situations when no customer notification is generated for the whole day.

      If such alarms existed, any JIRA Service Desk manager would know about issues with customer emails after one day instead of three (or more).

          Form Name

            [JSDSERVER-5302] Service Desk customer notification audit

            Charlie Marriott added a comment -
            Atlassian Update – 27 Jan 2021

            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

            Charlie Marriott added a comment - Atlassian Update – 27 Jan 2021 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

              Unassigned Unassigned
              1dbd5ff0cf83 Dastin Kuwałek [SoftwarePlant]
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: