Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-14260

Create Issue from Email Handler - Create Username Flexibility

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      When using the CreateOrComment handler to create first-time users who create issues based on email-address, it would be nice to be able to customize the format in which their user name is created. For example, we have an LDAP implementation that matches our users names: uname@foobar.com - their LDAP login is uname - but their user account is created as uname@foobar.com

      I know a current workaround exists (by modifying the code), but in the future would there be some application-UI-provided way to alter the format (regexp or otherwise) in which new user accounts are created via email to accommodate this and similar configurations?

            [JRASERVER-14260] Create Issue from Email Handler - Create Username Flexibility

            Josh Devenny added a comment -

            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
            Josh Devenny and Roy Krishna
            JIRA Product Management

            Josh Devenny added a comment - 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 Josh Devenny and Roy Krishna JIRA Product Management

            Andy Brook (Javahollic Software) added a comment -

            JEMH supports a couple of variations on user id selection for user creation by email, it does support "user@place.com" as well as "user", but most importantly, for those with LDAP based users, it will also enable a reverse lookup via LDAP, of that address, to discover the userID of the associated email address...

            Andy Brook (Javahollic Software) added a comment - JEMH supports a couple of variations on user id selection for user creation by email, it does support "user@place.com" as well as "user", but most importantly, for those with LDAP based users, it will also enable a reverse lookup via LDAP, of that address, to discover the userID of the associated email address...

            tim feeley added a comment -

            I'm not sure if the Atlassian LDAP implementation (JRA-1962) scheduled for the future will address some of these concerns.

            tim feeley added a comment - I'm not sure if the Atlassian LDAP implementation ( JRA-1962 ) scheduled for the future will address some of these concerns.

            tim feeley added a comment -

            This was originally input as a support request (JRA-14235), however it might merit discussion as an improvement for users with similar problems.

            tim feeley added a comment - This was originally input as a support request (JRA-14235), however it might merit discussion as an improvement for users with similar problems.

              Unassigned Unassigned
              2b4372e69789 tim feeley
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: