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

When creating user from a handler, the creator in the email notifciation is null

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • Hide

      Atlassian Update – 04 July 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 04 July 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

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

      These are the samples:

      • Created from JIRA UI 
        A JIRA account has been created for you at:

   http://10.60.1.148:8080/jira

This is either because an administrator has created an account for you,
or because you have been assigned to an issue.

You can change your password here:

   http://10.60.1.148:8080/jira/secure/ViewProfile.jspa

Here are the details of your account:
---------------------------------------------------------------------
            Username: tchin@atlassian.com
               Email: tchin@atlassian.com
           Full Name: tim
            Password: tim
(You can always retrieve these via the "Forgot Password" link on the signup page)
This action was initiated by Timothy Chin (topcat.38@gmail.com).
      • Created from handler 
        A JIRA account has been created for you at:

   http://10.60.1.148:8080/jira

This is either because an administrator has created an account for you,
or because you have been assigned to an issue.

You can change your password here:

   http://10.60.1.148:8080/jira/secure/ViewProfile.jspa

Here are the details of your account:
---------------------------------------------------------------------
            Username: tchin@atlassian.com
               Email: tchin@atlassian.com
           Full Name: Timothy Chin
            Password: 71icT6
(You can always retrieve these via the "Forgot Password" link on the signup page)
This action was initiated by null (null).

      Both email templates use the usercreated.vm template which has this line:

      usercreated.vm
      $i18n.getText("template.user.initiatedby", $initiatingUser.fullName, $initiatingUser.email)

              Unassigned Unassigned
              tchin Timothy Chin [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: