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

Customer satisfaction surveys allow customers to re-submit their scores multiple times

    • 0
    • 7
    • 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.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Summary

      JIRA Service Desk allows the customer to complete the CSAT survey multiple times, therefore ,allowing the customer to change his score and comments at any time.

      Steps to Reproduce

      1. Enable CSAT for the project
      2. Resolve an issue
      3. Customer will get resolution notification and the option to score the CSAT
      4. Customer fills survey and comments
      5. Agent will be able to view this in the backend
      6. Customer can come back at any time to this resolution email and can click on the survey link

      Expected Results

      Service Desk should inform the customer that he has already completed the survey.

      Actual Results

      The customer is able to refill the form and this will replace the previous survey filled by the customer

            [JSDSERVER-3839] Customer satisfaction surveys allow customers to re-submit their scores multiple times

            Atlassian Update – 1 March 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 – 1 March 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

            Is not possible to get report when satisfaction can be changed any time.

            Maro Hamamjyan added a comment - Is not possible to get report when satisfaction can be changed any time.

            Abernacky added a comment -

            Btw this sounds like a bug not a suggestion, at least to me

            Abernacky added a comment - Btw this sounds like a bug not a suggestion, at least to me

              Unassigned Unassigned
              mriza Mohamed Riza (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: