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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Set component based on e-mailadress the request was sent to

I'm really a beginner when it comes to Jira Service in general and automation specifically, so bare with me.

What I understand my question is probably simple but here goes:

I want to set component (and other parameters too but I'll just copy this one) based on e-mail address that was used by the person sending a request. So not from e-mail address.

How do I do this?

The workflows and issue types for our Jira service project are all standard.


1 answer

0 votes

Hi @Johan Bergström - Can you please clarify a couple things?

  • The person sending a request - Do you mean the Reporter?
  • Desired Component value - Using the example email address (, are you looking for it to be:
    • Entire email address (
    • Second Level Domain (SLD) and Top Level Domain (TLD) (
    • Just the SLD (example)
    • Just the mailbox (jsmith)
  • Most importantly, are the components already created?  If not, automation does not provide a mechanism for creating new components.  In this scenario, you may want to explore labels instead, but we can cross that bridge once we have a better understanding of your end goal.


  1. Yes - Reporter
  2. The entire email address 
  3. Yes, they are created


Mark Segall Community Leader Dec 07, 2022

Ok - This should be straightforward then.  You want something like this in its simplest form:

  • TRIGGER: Issue Created
  • ACTION: Log Action (This is a helpful step just to make sure we're capturing the right data)
    • {{issue.reporter.emailAddress}}
  • ACTION: Edit Issue (Component)
    • {{issue.reporter.emailAddress}}
Like Johan Bergström likes this

I'm sorry but I need a bit more help I think.

My case:

  • Email request is sent
    • If to: email address Is Equal to Then
      • Set specific Component

The key trigger is the email address, not from:email address

The scenario is to set different components depending on different to:email addresses. We want to set up unique email addresses for different customers that sets different components/labels.

FYI, did get the automation to work except I didn't know how to use  {{issue.reporter.emailAddress}} in

  • ACTION: Edit Issue (Component)
    • {{issue.reporter.emailAddress}}
Mark Segall Community Leader Dec 08, 2022

So you're looking for an incoming address?  Meaning... You're at company xyz.  You've set up multiple options for emailing (e.g.,, and they all create issues on this project.  Is this correct?

If this is the case, you're not going to be able to parse that information that I'm aware of.  Your best solution would be to tie each email address to a unique issue type so that you could automate or query against the issue type with knowledge that it was sent to the desired email.  Does this make sense?

Yes, that's correct.

Yes, I understand. I only have to figure out how to create unique issue types. Any hints on that...?

And how do I tie the unique email address to my unique issue type?

Mark Segall Community Leader Dec 08, 2022

As a Jira Admin, you can create new issue types under Settings >> Issues >> Issue Types

You would also need to set up email handlers for this which is not really my strength.  Are you on server or cloud?

Mark Segall Community Leader Dec 08, 2022

So after your issue types are created, you'd set up the email handler here:
Like Johan Bergström likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events