Creating issues in Jira by email

[Wendy Thorneloe]

Hi

My company has very strict security rules so they don't want to use the incoming mail option to create issues in Jira

Here is what My security guy says

Option 1:  Configuring a mail server/service in Jira – The problem with this option is that it requires GEM to allow anonymous POP or IMAP requests to our email service which is against our corporate security policy.

Option 2:  File system messages – This options avoids the security pitfalls of option 1 but it appears that GEM will need to host a version of Jira on premise in order to be able to write to the import/mail subdirectory.  Is this a correct assumption or are we missing something.  Please provide more details.

 Are there other options we can explore?

Thanks

Wendy

[Nic Brough -Adaptavist-]

Not really.  Your first option pretty much stops you dead.  You want to send email that get turned into issues, but your security people are effectively saying "you can't have email". 

On the second option, yes, you would need to install a Jira server locally, and have a way to convert incoming email to those files.

There is a third option (which works for Server or Cloud) would be to process the email somehow and generate REST calls into Jira to create the issues

You will note however, all of these methods require something to access the incoming mail, which is almost certainly going to have to be done with a system email user (not an anonymous one)

[Gregory Van Den Ham]

I'm confused... IMAP clearly lets you specify username/password for authentication into mail server.  This is not anonymous.  Documentation reference.

This might be a service account mailbox, like jira@whoever.com, but it can be managed.   

This is possible to do with Office365 E1 level licenses or general onprem mail servers.