nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Email to project - assignee by component

Alex Suslin

We have the single email address like help@company.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

Accepted answers

unknown

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.

All comments

Mizan

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 (

Assign to Lead Developer)

.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.

Alex Suslin

And how determain to which component lead I should assign the ticket?

Mizan

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 .

Mizan

Are you trying to create issues via emails ?

unknown

BTW, with JEMH 1.0, and Project Mapping, you could use a regexp to map specific to/from domain addresses to specific projects/components. I've not thought of doing that just for component filling but I don't see why it wouldn't work.

Alex Suslin

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 "helpdesk@company.com" 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?

unknown

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.