Does an email service need to be created for each Issue Type??

I read the issue creation though email documentation and I'm confused. Do I need to create one service per issue type, per project?

In other words, if I want to send an email to create, say, a subtask type issue, but my service is set up to type 1 (not subtask), then how would subtask be created? Do I specify that in the subject or body?

Also, I've been looking but haven't found a spot where there are examples of emails that one would send to create issues of different types.


1 answer

Yes, using the standard email handler, you would have to create a service for each issuetype you want created. I would use seperate addresses (catchemail) so the handler and service can properly process your messages (eg: create a bug vs sub-task)

If you want examples of ONE email that can create multiple issuetypes based on the content of that email, then you will need to use a different email handler. A good one would be JIRA Enterprise Mail Handler.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Agile

What is Scrum? A good, bad, and ugly answer.

In a world of dark-scrum, faux-scrum, and scrum-butt, the question still remains: What is scrum and how do you do it “right?” That’s the question we set out to answer. I'm Max, I've been teaching c...

57 views 0 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you