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; } } }

Mapping email - reporter

Daniel Garcia12

Hi,

I create new issues in project from email, but I want to 'map' (make relationship) email with a user in JIRA.

Let me explain, I have one user 'A' in Jira with email 'sample@jira.cat'. I want that if this user 'A' send email to a project, a new issue is created in which reporter is her jira user.

It is possible in Jira? Where I can configure this mapping email - username?

Thanks in advance!

Daniel

Accepted answers

Thomas Schlegel

Hi Daniel,

of course, this is possible. The reporter is generated automatically, if the sender's email-adress is already registered.

Look here for more information.

All comments

C_Faysal _CFcon_

Jemh is the plugin what you want to look at. It will offer a lot of options for email mapping.

https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui

Thomas Schlegel

doesn't this work with basic Jira functionality already ?

Thomas Schlegel

Hi Daniel,

of course, this is possible. The reporter is generated automatically, if the sender's email-adress is already registered.

Look here for more information.

C_Faysal _CFcon_

it does...but JEMH is way more configurable than jiras internal mail handler.

read the KB article thomas posted and compare with andy's documentation page

MatthewC

Daniel, go with Thomas-S' answer, just make sure that you don't have the same email address in more than more account. If you do, Jira may pick the wrong account which may not have access to the project. This is one use case where the "default" reporter will not work.

unknown

@Thomas-S, the built in functionality is good for creating a single user account based on incoming email address if that address is not already registered. They are many cases beyond this that won't work, which is where JEMH comes in.

One case JEMH covers include alternateID providers, a way to manipulate how JIRA userIDs get created, if a simple 'email' name is not acceptable/appropriate (like, what happens when the same user changes email provider?).

Another is when, in an LDAP enabled environment, users emails come literally from the same person but via different systems that use different LDAP proxyAddresses. Default handling in JIRA would then create new emails for each unique address. JEMH (in 1.3) can interrogate LDAP to determine a proxyAddress match, and correctly associate the incoming email with the pre-existing user.

Daniel Garcia12

Thanks!

This is the solution that I was looking for!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-service-desk

notification