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

Filter incomming e-mails

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Email notifications
    • None
    • 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.

      At the moment any incomming e-mail that JIRA processes to create an issue or a comment does not get inspected. So e-mail bounces create new issue or comments.

      A filter can be added to services to scan the entire message (including headers) before passing them to handlers. The filter can read a config file for regular expressions that should not allow the message to proceed if matched.

            [JRASERVER-7728] Filter incomming e-mails

            Josh Devenny added a comment -

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Josh Devenny and Roy Krishna
            JIRA Product Management

            Josh Devenny added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Josh Devenny and Roy Krishna JIRA Product Management

            Andy Brook (Javahollic Software) added a comment -

            For anyone passing, JEMH has the ability to filter (issue title), and to update custom fields as per comment 1, and its free

            Andy Brook (Javahollic Software) added a comment - For anyone passing, JEMH has the ability to filter (issue title), and to update custom fields as per comment 1, and its free

            AntonA added a comment -

            Adnan,

            I am glad you have thinsg working. If it is OK with you I will leave this issue open as we would like to actually get this done in JIRA. The only problem now is time and resources

            Thanks,
            Anton

            AntonA added a comment - Adnan, I am glad you have thinsg working. If it is OK with you I will leave this issue open as we would like to actually get this done in JIRA. The only problem now is time and resources Thanks, Anton

            Adnan Chowdhury [old] added a comment -

            We've created our own mail handler to satisfy our requirements here. This issue can be closed.

            Adnan Chowdhury [old] added a comment - We've created our own mail handler to satisfy our requirements here. This issue can be closed.

            AntonA added a comment -

            Hi Adnan,

            This issue is not really meant for the field population functionality. Please have a look at:
            http://confluence.atlassian.com/display/JIRAEXT/Pix+Email+Handler

            One of our partners has developed a custom handler to parse field values from e-mails.

            Anton

            AntonA added a comment - Hi Adnan, This issue is not really meant for the field population functionality. Please have a look at: http://confluence.atlassian.com/display/JIRAEXT/Pix+Email+Handler One of our partners has developed a custom handler to parse field values from e-mails. Anton

            Adnan Chowdhury [old] added a comment -

            The ability to handle name value pairs would be a great help as well. That is handle @fixinversion=6.7.8 and have that fill in the Fixed In Version custom field with this value.

            Something like the iPix mail handler plugin, but for free

            Adnan Chowdhury [old] added a comment - The ability to handle name value pairs would be a great help as well. That is handle @fixinversion=6.7.8 and have that fill in the Fixed In Version custom field with this value. Something like the iPix mail handler plugin, but for free

              Unassigned Unassigned
              anton@atlassian.com AntonA
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: