We have the single email address like email@example.com (Google Apps) and we got several offices (say in USA and Europe).
I have created the project HELPDESK in JIRA and 2 components like: USA and EUROPE.
I would like to assign tickets from USA employee to USA sysadmin and tickets from EUROPE to another person. So they are component leads in my project.
Anybody know the plugin that can help me to reach my goal?
Standard mail handler: I like that he can use IMAP folders to gather emails from. So I can setup 2 email handlers and in google apps (gmail) create some filters to separate USA employee from europe ones (and lable them). And in handlers grab emails from specific label to create an issue. However standard mail handler can be linked to a project only.
I have investigated JEMH plugin, however I haven't found an easy way to assign it to a component. I don't want users remember directives and put something like "component: USA" in every email. You know it's a crunch and easy to forget about that.
Idially I'd like to combine the standard Email Handler (IMAP Folders option) with JEMH (assign issues to component leader). Any options?
Thanks in advance
No, the legacy configuration file supports only a subset of prior functionality, no new functionality and won't ever be extended. In its current form, it's expected to only be usable in 'unlicensed' mode but I broke it during RC when forward email configuration was pulled into JEMH, I have yet to fix it, but is on my short list to fix.
The Project Mapping features in JEMH 1.0+ were specifically implemented to address mapping sender domain/addressee to specific project components, based on the scenario you presented. You will need the UI in order to do that.
Hi Alex ,
>I would like to assign tickets from USA employee to USA sysadmin and tickets from EUROPE to another person. So they are component leads in my project.
There is a default Post function available in Jira which Assigns the issue to Lead Developer/Component Manager (
.You can use this postfunction on the create transition/step of your workflow. This will automatically assign the issue to the Component lead based on the component selected while creating the issue
However the email will be sent to the same email id.
When you select USA as a component while creating the ticket the ticket will be automatically assigned to the Component Lead of USA similarly for component Europe.
And for the email i dont know how but i guess you will have to do something with message rules if you are using outlook .
The question was related to Mail Handler. It is not related to any mail client (like outlook or web interface). The Handler is grabbing the mail directly from the server and creates an issue in JIRA. So if you read the post till the end you found that I can setup email handler to grab issue from the IMAP folder (and in that particular case the folder name is the component in JIRA project). But with postfunctions I have no that information, so the question was how to combine out-of-the box mail handler with the possibility to assign issues to component lead (that can be reached with the help of JEMH plugin).
And yes I'm trying to create issues via email, doesn't that obvios from the subject?
I don't need the project mapping as I have single project HELPDESK. I don't need specific to / from. "To" will be always the single email "firstname.lastname@example.org" and from may be one of the our employee (~150 different email addresses). And how that helps me to assign issue to a component without having component derective in email itself?
Are you 150 email addresses of a common domain, or split over many countries? How many domains are we talking about?
The Project Mapping stuff can be applied to email addresses at domain level, and can determin a project, component and assignee (whether that assignee is the component owner or not). This route would naturally result in n mappings, for the number of domains you have. Of course, if you have a single domain, that wont work, and you'll need some other way to differentiate, eg groups.
The Project Mappings in JEMH can also route messages based on the JIRA group membership, so all 'US' group members would get funnelled into component X. Combining the two isnt something Ive tried yet, adding a wildcard project mapping after a gorup mapping would achieve what you are trying to do, something I should look at as its just a logic issue as to which one goes first.
Let me know if you want to pursue/test.
Hi Alex, doco is a weakness at the moment, working on it, meantime, for a single group see https://studio.plugins.atlassian.com/wiki/display/JEMH/Routing+issues+to+a+project+-+by+user+group+membership
For anyone not wanting to script their own solution. Mapping of inbound groups (and email to/from) to Project and per-mapping Component now implemented in JEMH, (RC2 out later today) , see doc's https://studio.plugins.atlassian.com/wiki/display/JEMH/Project+Mapping+%28group%29+-+example
Andy, I've come into a problem with non-jira users, so my script is needed to be enriched or either we'd need to use your plugin... however I need to test it, is it possible to achive that groups assignment without GUI interfece? just don't know the name of fields that needed to be used there (I mean config file)
Hi all I'm able to solve my question with the help of
* Out of the box jira mail handler
* Script runner plugin and custom-written groovy script
* Changing workflow and adding post function on creation step.
You may find useful to see how to achive that in details here:
I have written a blog post about that.
Hope that helps,
Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot