-
Suggestion
-
Resolution: Won't Fix
-
None
-
Standalone on linux with tomcat/mod_jk
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Currently all users created by the autocreate=true option in the mail service are created with the email address. As most of our users have LDAP accounts (with the same name as the username in the email) it would be nice to create accounts for them that can be used with the LDAP. This could be done in two ways that I can think of: the easier (and one I would at some level prefer) is to have an ignore domain flag in the service options. We would set ignore_domain=example.com and it would create new users with just the local part of their email addresses.
The other way would be to do some validation/checks on the backend data source, but that is going to be a great deal more complex.
- duplicates
-
JRASERVER-14973 AbstractMessageHandler patch (provides pluggable findUserByEmail, and external property file support for handler params + inbound issue creation fixes for Component,Priority,IssueType,Assignee)
- Closed
- is superseded by
-
JRASERVER-14973 AbstractMessageHandler patch (provides pluggable findUserByEmail, and external property file support for handler params + inbound issue creation fixes for Component,Priority,IssueType,Assignee)
- Closed
- relates to
-
JRACLOUD-12945 Remove the domain part of email address when autocreating users
- Closed
Hi,
This is a bulk update to specific issues in the JIRA (JRA) project
As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.
Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com
If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.
Best regards
Roy Krishna and Josh Devenny
JIRA Product Management