Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-2456

Email handlers should send email back upon rejection.

    • We collect Jira 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 Server. Using JIRA Cloud? See the corresponding suggestion.

      If an error occurs when a comment handler is processing an email message, the message is left in the email spool and will continue to generate an error message in the logfile. A typical error that we envision is a user sending an email from a different email account where the return address doesn't match the user's address in the database.

      The problem is that nobody is notified that the error has occurred and the comment is lost until someone stumbles across it. It would be better if an email was sent back to sender indicating that an error occurred.

            [JRASERVER-2456] Email handlers should send email back upon rejection.

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            JEMH has loop detection through jemhAdressee and catchEmail addresses, and will reject back to the user if configured to do so..

            @matt JEMH also provides ability to configure a 'user did not provide a subject' placeholder message. All notifications are toggleable.

            Andy Brook (Javahollic Software) added a comment - JEMH has loop detection through jemhAdressee and catchEmail addresses, and will reject back to the user if configured to do so.. @matt JEMH also provides ability to configure a 'user did not provide a subject' placeholder message. All notifications are toggleable.

            linking mail loop bug. whenever JIRA bounces forwards or otherwise sends email, we need to consider the possibility of mail loops.

            Chris Mountford added a comment - linking mail loop bug. whenever JIRA bounces forwards or otherwise sends email, we need to consider the possibility of mail loops.

            Just another note: Our top driver for this is that users quite often will dash off a support email without putting anything into the subject line. the CreateOrComment handler does not like this, but the user never gets direct feedback about it. I think if they got an immediate email about it, they'd resubmit the ticket with a subject, saving us a lot of time and hassle.

            Matt Kenigson added a comment - Just another note: Our top driver for this is that users quite often will dash off a support email without putting anything into the subject line. the CreateOrComment handler does not like this, but the user never gets direct feedback about it. I think if they got an immediate email about it, they'd resubmit the ticket with a subject, saving us a lot of time and hassle.

            This is an important issue for us. It's good that we now know that something happened but it would help even more if our users did, too. It should be toggleable, though, as we wouldn't want to implement it that way for some sensitive "queues".

            Matt Kenigson added a comment - This is an important issue for us. It's good that we now know that something happened but it would help even more if our users did, too. It should be toggleable, though, as we wouldn't want to implement it that way for some sensitive "queues".

            BrianH added a comment -

            The Email Handlers will now forward emails to a particular email address if an error occurs.

            However it does not yet return email to sender.

            BrianH added a comment - The Email Handlers will now forward emails to a particular email address if an error occurs. However it does not yet return email to sender.

              Unassigned Unassigned
              38a17e3694df Steve Bachinsky
              Votes:
              8 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: