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

Notification for when an email is failed to processed or rejected for Service Desk project

    • 35
    • 17
    • 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 Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      Current Behaviour
      All the information can be found in the Service Desk mail log. Service Desk Mail log requires user to constantly monitor the log to see if a ticket has failed or not. It would be great to receive a notification like how JIRA does.

      • JIRA Email handling error:

          Form Name

            [JSDSERVER-2517] Notification for when an email is failed to processed or rejected for Service Desk project

            Hello Jira Support,

            is anybody here? We are paing lot of money for unsupported products?

            THANKS.

            Martin Sagan added a comment - Hello Jira Support, is anybody here? We are paing lot of money for unsupported products? THANKS.

            Is there a recommended work-around?

            We just moved from on-prem to the cloud version and are shocked, that the users don't get any feedback if their ticket is not created. That is a serious step backwards.

            petr.beles@datavault-builder.com added a comment - Is there a recommended work-around? We just moved from on-prem to the cloud version and are shocked, that the users don't get any feedback if their ticket is not created. That is a serious step backwards.

            How it's even possible to have open ticket for eight years ? Either close it with 'we don't consider this as a issue' or fix this please. Or are you not done with gathering interest after 8 years ? Please.

            Martin Majtan added a comment - How it's even possible to have open ticket for eight years ? Either close it with 'we don't consider this as a issue' or fix this please. Or are you not done with gathering interest after 8 years ? Please.

            Any news with this bug?
             
             
            Nejake novinky s touto chybou?

             

            Martin Sagan added a comment - Any news with this bug?     Nejake novinky s touto chybou?  

             There is a log entry in Application-> Email Requests -> View 

            • but this can only be view by the sysadmin
            • involving the sysadmin for every little email is not practical

             its badly needed and should be configured like other notifications

            Fides IT Admin Account added a comment -  There is a log entry in Application-> Email Requests -> View  but this can only be view by the sysadmin involving the sysadmin for every little email is not practical  its badly needed and should be configured like other notifications

            +1 its badly needed

            Pierre Kroll added a comment - +1 its badly needed

            +1 I was very surprised this didn't already exist. 

            Brett Latham added a comment - +1 I was very surprised this didn't already exist. 

            Ok how the hell is this an optional feature request gathering interest for seven years? 

            Informing users when a function fails is basic usability and design practice. I was just informed that a customer will switch to another solution because users never know if an issue was created or not. Users there regularly include non-customers in CC, and such an email is dropped instead of creating the request without adding the CC'ed mail participants. Such requests vanish in limbo, the customer is not informed that their mail did not result in a request. this is a miserable user experience.

             

            Martin Hilbig [team neusta] added a comment - Ok how the hell is this an optional feature request gathering interest for seven years?   Informing users when a function fails is basic usability and design practice. I was just informed that a customer will switch to another solution because users never know if an issue was created or not. Users there regularly include non-customers in CC, and such an email is dropped instead of creating the request without adding the CC'ed mail participants. Such requests vanish in limbo, the customer is not informed that their mail did not result in a request. this is a miserable user experience.  

            As we are combining two companies we are manually adding "customers" so that they can send requests. There were some emails missed while adding and no one knew their request never came in.

            This should be added to "customer notifications" and allowed to be edited.

            Justin Van Syoc added a comment - As we are combining two companies we are manually adding "customers" so that they can send requests. There were some emails missed while adding and no one knew their request never came in. This should be added to "customer notifications" and allowed to be edited.

            We just caught a sign-in failure for our email queue on a client with high ticket volume.  It had been failing to connect for 20 hours, and we are now catching up on 200+ issues.

            This is needed.  Any type of notification that email notifications are failing is a must.

            Malachi C. Smith added a comment - We just caught a sign-in failure for our email queue on a client with high ticket volume.  It had been failing to connect for 20 hours, and we are now catching up on 200+ issues. This is needed.  Any type of notification that email notifications are failing is a must.

              Unassigned Unassigned
              mariffin Mohamed Hazwan Ariffin (Inactive)
              Votes:
              240 Vote for this issue
              Watchers:
              142 Start watching this issue

                Created:
                Updated: