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

UserCreationListener e-mail spam during JIRA migration

    XMLWordPrintable

Details

    • Severity 2 - Major
    • Hide
      Atlassian Update – 06 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 06 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

    Description

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

      In jira-ondemand-project/jira-ondemand-plugins/jira-ondemand-theme-plugin/src/main/java/com/atlassian/studio/jira/haup/UserCreationListener.java the following code currently exists:

              for (com.atlassian.crowd.embedded.api.User user : userUtil.getAllUsersInGroups(permissionManager.getGroupsWithPermission(Permissions.ADMINISTER)))
              {   
                  Email email = new Email(user.getEmailAddress());
                  email.setSubject(i18n.getText("studio.jira.email.grant.failure.conflictnotification.subject"));
                  email.setMimeType("text/html");
                  email.setBody(emailBody);
                  mailQueue.addItem(new SingleMailQueueItem(email));
              }   
      

      As everyone on jira-dev (and many people outside of jira-dev) noticed when 2 migrations I attempted failed to upgrade over 100 of the users, spamming one e-mail per failed user is really unacceptable. This needs to be changed to coalesce multiple failures with the same target address.

      It looks like onUserCreation also tries to exempt UserCreatedFromDirectorySynchronisationEvent messages, so perhaps doing something similar to ignore failures during data migration would be a simpler option.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cfuller crf
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: