Email handling licencing

How does licensing work for email-this issue & JIRA v7?

We are on JIRA v 6.3 now which has no cost associated for email handling but are of the understanding that with v7 JIRA this now comes at quite a cost?

If we were to license email-this-issue (which sounds very cool) would this negate the need to license JIRA email handling? Or is JIRA email licensing a pre-requisite for email-this issue in v7?

1 answer

1 accepted

This widget could not be displayed.

Email handling is part of JIRA out of the box, you don't need to license it separately. 

Email This Issue's email handling capabilites go much beyond what JIRA can do and add a lot more functionality.

There is a comparision this in this page: https://www.meta-inf.hu/display/PLUG/Email+This+Issue+Features

Thanks for the reply.

Yes it definitely is with v6x but appears to not be with v7x? This is what's confusing me...

Essentially we have a lot of clients that email in without the need for a JIRA account & the emails get recieved by JIRA & auto-converted into an issue.

Below is from the JIRA 7x release notes:

------

Changes to issue creation via email

In previous versions of JIRA, users without the JIRA Users Global Permission were not able to log in to JIRA, but if they belonged to a group that had Create Issue permission for a project, they could create issues via email if a JIRA email handler was set up. 

In JIRA Software, you must have application access to the JIRA instance in order to create issues, regardless of how the issue is created. This essentially means that:

  • you won't be able to create issues via a JIRA email handler if you don't have application access, and
  • the JIRA email handler has not been set up to create a new user account with application access for you.

We have made this change to introduce more consistency in how licenses are enforced in JIRA applications.

------

https://confluence.atlassian.com/jirasoftware/jira-software-7-0-0-release-notes-776997721.html


I definitely agree that email-this-issue adds a lot of extra email features over JIRA out of the box -however that is not my question.

Appreciate your help

Hi David,

In your case it means that your clients will still be able to send emails and JIRA or JETI will be able to process them. Your mail handlers must be setup with a default reporter. The default reporter needs to be a user with permissions to create issues or comments in the project.

If a client sends an email, JIRA/JETI will create the issues with the default reporter as the Reporter of the issue. Similarly, comments will be added by the default reporter on behalf of the client.

The above explanation was related to a case where clients were setup as JIRA users without permissions to log in to JIRA (hence they did not take license) and this is not possible any longer in JIRA 7.

To put it short, if your clients are not registered in JIRA as users, then it will work for you as it did with JIRA 6.

Tibor

That makes sense. Appreciate your assistance.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in Statuspage

What are your best incident management tips and stories? #HugOps

 👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...

69 views 2 3
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you