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

As a Service Desk Admin, I would like to blocklist certain email address from creating issues

    • 15
    • 8
    • 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.

      Atlassian Update – 20 Sept 2022

      Hi all,

      Thank you so much for your votes and comments on this suggestion. We are currently working on a solution for this ticket. We have a few open questions about the design of this feature and would love to hear your feedback. Please send an email to lwalsh2@atlassian.com if you would like to join a 45-minute session over video conference on this topic in the next couple of weeks. In the email, please include the following details:

      • your company’s industry
      • the size of your company
      • how your company uses Jira Service Management (JSM)
      • a summary of how this problem affects your team

      Although we can't guarantee that we will be able to speak with all interested parties, we definitely appreciate your interest and enthusiasm to help us make JSM DC easier and more enjoyable to use.

      Thanks,

      Lisa

      Problem Definition

      Currently, if you want to blocklist a spam email, then you have to mark it as spam from the mail server itself. However, in large organisations where we have separate admins for Jira and mail servers, then it would troublesome to regularly sent requests to the mail server admins to set email addresses as spam.

      Suggested Solution

      Allow Jira admins to set emails as spam from Jira itself, so Jira will not process emails from the blocklisted email address.

          Form Name

            [JSDSERVER-3836] As a Service Desk Admin, I would like to blocklist certain email address from creating issues

            Lisa Walsh added a comment -
            Atlassian Update – 20 Sept 2022

            Hi all,

            Thank you so much for your votes and comments on this suggestion. We are currently working on a solution for this ticket. We have a few open questions about the design of this feature and would love to hear your feedback. Please send an email to lwalsh2@atlassian.com if you would like to join a 45-minute session over video conference on this topic in the next couple of weeks. In the email, please include the following details:

            • your company’s industry
            • the size of your company
            • how your company uses Jira Service Management (JSM)
            • a summary of how this problem affects your team

            Although we can't guarantee that we will be able to speak with all interested parties, we definitely appreciate your interest and enthusiasm to help us make JSM DC easier and more enjoyable to use.

            Thanks,

            Lisa

            Lisa Walsh added a comment - Atlassian Update – 20 Sept 2022 Hi all, Thank you so much for your votes and comments on this suggestion. We are currently working on a solution for this ticket. We have a few open questions about the design of this feature and would love to hear your feedback. Please send an email to lwalsh2@atlassian.com if you would like to join a 45-minute session over video conference on this topic in the next couple of weeks. In the email, please include the following details: your company’s industry the size of your company how your company uses Jira Service Management (JSM) a summary of how this problem affects your team Although we can't guarantee that we will be able to speak with all interested parties, we definitely appreciate your interest and enthusiasm to help us make JSM DC easier and more enjoyable to use. Thanks, Lisa

            we have used a workaround to block tickets from other ticketsystems.

             

            -> usercontrol/userbrowser https://XXXXX/secure/admin/user/UserBrowser.jspa

            -> create new user with that emailadress or search for that user with the to blocking mailadress and set this account to inactiv.

             

            now that user cannot create or comment a issue.

            Georg Maertin added a comment - we have used a workaround to block tickets from other ticketsystems.   -> usercontrol/userbrowser https://XXXXX/secure/admin/user/UserBrowser.jspa -> create new user with that emailadress or search for that user with the to blocking mailadress and set this account to inactiv.   now that user cannot create or comment a issue.

            Hi.. we need this blacklist feature as well. It's so annoying to have spam mails created as a ticket.... please add this feature.

            Rene Knogler added a comment - Hi.. we need this blacklist feature as well. It's so annoying to have spam mails created as a ticket.... please add this feature.

            Atlassian team, can we get some action on this please?

            Michael Woffenden added a comment - Atlassian team, can we get some action on this please?

            We are interested to get license/subscription for one of our client.
            Basically we will buy it for our client to use. I hope this would be fine, please let us know if you have any observation.

            Implevista Development team added a comment - We are interested to get license/subscription for one of our client. Basically we will buy it for our client to use. I hope this would be fine, please let us know if you have any observation.

            Any Update on this?

            Rohit Singh added a comment - Any Update on this?

            Chris added a comment -

            Any updates on this request?

            Chris added a comment - Any updates on this request?

            One suggestion to address this would be to enhance the functionality of Automation.  I can check for incoming mail from a particular account and perform a number of actions on it including responding to the request and transitioning the request.  I could transition to Close the ticket but that impacts my SLA's.  If there was an option to delete the incoming request it would, I think, address the need. 

            Robert Faille added a comment - One suggestion to address this would be to enhance the functionality of Automation.  I can check for incoming mail from a particular account and perform a number of actions on it including responding to the request and transitioning the request.  I could transition to Close the ticket but that impacts my SLA's.  If there was an option to delete the incoming request it would, I think, address the need. 

            Also need this function. Zendesk has the ability for black and white listing.

            Reiss Snooks added a comment - Also need this function. Zendesk has the ability for black and white listing.

            We have a few companies that occasionally send out non-opt-out automated emails to our support email. The simplest solution would just be to blacklist their emails.

            One example of this is a manufacturer who sends us notices when one of our customers violates MAP. These are irrelevant to us and the company ignores any attempt to explain to them they have the wrong company. I'm sure there are plenty of other scenarios where it would be nice to blacklist, and having it within JIRA makes one easy place to manage things rather than jumping between the email server and JIRA.

            William Wynn added a comment - We have a few companies that occasionally send out non-opt-out automated emails to our support email. The simplest solution would just be to blacklist their emails. One example of this is a manufacturer who sends us notices when one of our customers violates MAP. These are irrelevant to us and the company ignores any attempt to explain to them they have the wrong company. I'm sure there are plenty of other scenarios where it would be nice to blacklist, and having it within JIRA makes one easy place to manage things rather than jumping between the email server and JIRA.

              cmarriott Charlie Marriott
              mriza Mohamed Riza (Inactive)
              Votes:
              59 Vote for this issue
              Watchers:
              41 Start watching this issue

                Created:
                Updated:
                Resolved: