I have issues coming into several e-mail addresses, which are then forwarded to the JIRA e-mail. Is there any way to create an automation around that?
Example: All e-mails sent to gdpr@company.com should be forwarded to the person responsible for GDPR.
OK all.
There IS a way to solve this.
So... firstly you can interrogate the email logs using an API call from within an automation. This can be useful in many ways, such as responding to Failed emails etc.
The web Request should be formatted like this:
https://destinygroup.atlassian.net/rest/jira-email-processor-plugin/1.0/mail/audit/process/CHANNELdefa82dab753?from={{epochtimestamp}}&statuses=NEW%20REQUEST
Explanation:
The CHANNEL and ID are pulled from the logs using the Inspect or Console browser tool. You'll need to do this manually once for each message so you can build your rule.
The epochtimestamp is created within the automation to the period you wish to search from.
The statuses are the stauses of the log messages where 'NEW REQUEST' is a successful email that has created a valid ticket.
So now you can build your automation like this;
So the epochtimestamp here is set to 1 minute before now (in order to search the logs for the past minute)
Now we issue our Web Request. Here's the configuration:
Now, for each email address you will need to branch out to perform some tests:
What we are doing here is creating a variable called webKey from a value captured in the webResponse by branching on the webData field:
Now you have extracted an issue.key from the response of your Web Request, you can compare it to the actual issue.key of the Trigger issue.
If it's a match you can perform an action such as enter a value into a custom field to identify a Support Queue.
As mentioned, the above, you need to repeat the branch for every email address, which means you also need to repeat the WebRequest using a different Channel ID.
This works well albeit being a tad 'clunky'.
Do the from emails resolve to the Reporter or in some manner captured in the created issue? If so then you should be able to use Automation to assign them based upon that info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you mean if the original recipient is shown as sender in the received e-mail in JIRA, then the answer is no. The original sender is shown as sender. The forwarding service forwards the mail as-is.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
no I meant the original sender is maintained which it seems to be the case. So the original sender is recorded as the Reporter of the issue, correct? If so then automation would be something like this...
trigger - issue created
condition - if/else block inspecting reporter (issue field condition Reporter = xxxxx)
action - assign issue based on reporter (edit issue assignee)
each reporter would have a condition and action
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I have a similar query here. We have several email ALIASES all redirecting to the same email INBOX. This inbox is connected to Jira Service Cloud that creates a new issue/ticket for each new email received. eg. support@ourdomain.com and gdpr@ourdomain.com both redirect to the same inbox/Jira email handler.
We would like to create an automation rule based on the recipient (not the sender) of that email (eg. if recipient = gdrp, do this, else if recipient = support, do that)
I doubt it is possible without using a mail handler extension but maybe there is a workaround?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Matthias, i have the same question... do you have an solution in the meantime? Best Regards Matthias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Has there been any further thoughts in this area?
Like those above, I have several email addresses linked as incoming addresses in my project and need to apply some form of automation to each, to ensure the correct team handle them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.