Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,866
Community Members
 
Community Events
184
Community Groups

Trigger automation based on e-mail recipient

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.

1 answer

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 19, 2022

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.

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.

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 19, 2022

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

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?

Like # people like this

Hi Matthias, i have the same question... do you have an solution in the meantime? Best Regards Matthias

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events