-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Jira 4.0 introduced user based licensing. Customers that use the 'createusers' option in one of their mail handlers have little control over the amount of users that their instance has. This is because every user created from the mail handler is assigned to the "JIRA Users" global permisisons, and therefore, they are granted permission to log into Jira, increasing the number of active users by one.
For customers that only want these users to interact by email (and therefore they do not need to log into Jira) it would be useful to have an extra parameter in the mail handler to indicate that the new user should not be granted "Jira Users" global permission.
To make sure these new users do receive mail notifications when the issue is updated, the browse project permission for the relevant project should be granted to group (anyone)
- relates to
-
- Closed
[JRASERVER-19509] Add parameter to email handlers not to add new users to the "JIRA Users" global permisisons
Bogdan Dziedzic [Atlassian]
added a comment - Feedback from a customer reporting issue with Support:
...I assume the answer is yes but I'll ask to make sure. In the case of using Jira as a support platform, do end users submitting issues need to be licensed in order to get notifications? The reason I ask is because running Greenhopper seems to require the same number of Greenhopper licenses as Jira licenses. I need at most 20 licenses for Greenhopper, but I would need 50-100 Jira licenses for support. It just doesn't make sense to by 50-100 Greenhopper licenses.
Bogdan Dziedzic [Atlassian]
added a comment - Feedback from a customer reporting issue with Support:
...I assume the answer is yes but I'll ask to make sure. In the case of using Jira as a support platform, do end users submitting issues need to be licensed in order to get notifications? The reason I ask is because running Greenhopper seems to require the same number of Greenhopper licenses as Jira licenses. I need at most 20 licenses for Greenhopper, but I would need 50-100 Jira licenses for support. It just doesn't make sense to by 50-100 Greenhopper licenses. 
Andy Brook (Javahollic Software)
added a comment - I've just released JEMH v0.9.4.3 which does exactly this.
Andy Brook (Javahollic Software)
added a comment - I've just released JEMH v0.9.4.3 which does exactly this. 
Toby Jackson
added a comment - This issue is causing me some problems as well; I'm basically looking for the following functionality;
- Create issues by Email [Done]
- Assign the originators email address as a "Watcher" (for instance) on the issue such that
- When I comment on the issue or it is resolved etc the originator gets an email directly about the change.
I don't require the user to be able to login and review the issues etc, but the communication back to the originator is the main objective.
Toby Jackson
added a comment - This issue is causing me some problems as well; I'm basically looking for the following functionality;
Create issues by Email [Done]
Assign the originators email address as a "Watcher" (for instance) on the issue such that
When I comment on the issue or it is resolved etc the originator gets an email directly about the change.
I don't require the user to be able to login and review the issues etc, but the communication back to the originator is the main objective. 
Tom Keating
added a comment - This is very important as a new email adds to the user license incorrectly
Tom Keating
added a comment - This is very important as a new email adds to the user license incorrectly 
Deleted Account (Inactive)
added a comment - Would really appreciate it if this was implemented soon!
Deleted Account (Inactive)
added a comment - Would really appreciate it if this was implemented soon! 
Thanks for taking the time to raise this issue.
Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.
I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.
Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com