Following an earlier answer I have set up JEMH on our instance of JIRA to capture the email address of users who do not have a JIRA account and store it in a custom field (cunningly named "Email Address") using the assignNonJiraUsersOriginalEmailAddressToCustomField directive. Having done this, I have now been asked if I can extract the name of the person and put that into a custom field too.
I can see tha JEMH is capable of extracting a name from an email address e.g. firstname.lastname@example.org when using the createUsersIDFrom=name directive.
Does a assignNonJiraUsersOriginalNameToCustomField (or similar) directive exist? Would it recognise when the name is passed along with the email address i.e. Name <email@example.com>?
Currently the name part is ignored, as its optional, adding support is of course possible.
It's possible a simple text field could have 'whatever' was provided injected, instead of a usable firstname.lastname@example.org address, but perhaps an email custom field would more useful, allowing extraction of the information. Which would work best in your scenario, two fields 'deformatted' or one containing arbitrary string quotes or not, depending on the whim of the server?
In the first instance I was thinking the easiest thing would be to have two separate "simple text" fields, one for the "Display Name" and one for the "Email Address". Then, much like Outlook (or other email clients), the senders address is parsed into these two parts and saved accordingly based on the configuration directives.
Admittedly the Display Name will not be perfect and is dependent on the server. However, if it does not exist (or cannot be parsed) it could fallback to using the email alias.
This logic could be wrapped into a custom Email Address field as you suggest, which stored the unparsed senders address in the supplied format (e.g. email@example.com or "Name [firstname.lastname@example.org]" or "Name <email@example.com>" etc). The view template for the field could then display the information in a usable form - perhaps a mailto: link with the subject set to the summary and issue key and the cc set to the email address for the JIRA project.
If it could be included that would be helpful as our instance of JIRA allows email submissions from non-corporate users so their email address does not always give away their name :)
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot