Uploaded image for project: 'Identity'
  1. Identity
  2. ID-93

Allow for custom emails being sent to welcome new users

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem statement

      The latest new user email read as follows:

      Subject: [Atlassian] USERNAME, welcome to Atlassian OnDemand
      Sent by: jira@example.atlassian.net

      Message: Your OnDemand account has been created! Atlassian OnDemand is the à la carte hosted development and collaboration solution for teams building great software. Log in now to track your issues and tasks, collaborate with your team, and stay on top of project activity.

      • Receiving emails from jira@example.atlassian.net can be confusing when invited users will only use Confluence.
      • This causes support issues as the new user email is getting ignored or deleted by users.

      Suggested solution

      1. Can the invitation be sent from cloud@example.atlassian.net?
      2. Can the message be more generic - not every Cloud customer is using it for "building great software". I've attached the old Confluence OnDemand invitation for reference: confluenceinvitemessage.png.

      Ideally, the Cloud site administrators should have the ability to create a custom message template.
      We actually send out a 2nd follow up message to this invitation that also cover tips such as reminders to set their time zone, setting a default landing page, notifications and where to get more help.

            [ID-93] Allow for custom emails being sent to welcome new users

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3258670 ] New: JAC Suggestion Workflow 3 [ 3644673 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Michael Andreacchio made changes -
            Workflow Original: ACCESS Suggestion workflow [ 3156882 ] New: JAC Suggestion Workflow [ 3258670 ]
            Katherine Yabut made changes -
            Workflow Original: reviewflow [ 787522 ] New: ACCESS Suggestion workflow [ 3156882 ]
            Rockert (Inactive) made changes -
            Component/s Original: User management [ 33497 ]

            We're in the process of rolling out Atlassian account support to Atlassian customers. Find out more here: https://confluence.atlassian.com/display/Purchasing/Introducing+Atlassian+account  

            As part of this, we've added the ability to customise an invite email's text at the point of invite, and the email now references the products that are in use, so are hopefully more useful for the users. 

            In the next day or two, all customers should be able to opt-in to Atlassian account in order to unlock these capabilities. 

            Rusty (Matt) (Inactive) added a comment - We're in the process of rolling out Atlassian account support to Atlassian customers. Find out more here: https://confluence.atlassian.com/display/Purchasing/Introducing+Atlassian+account    As part of this, we've added the ability to customise an invite email's text at the point of invite, and the email now references the products that are in use, so are hopefully more useful for the users.  In the next day or two, all customers should be able to opt-in to Atlassian account in order to unlock these capabilities. 

            I see this issue has just been resolved, however there is no information on what has been done.

            Hilary Boyce added a comment - I see this issue has just been resolved, however there is no information on what has been done.
            Rusty (Matt) (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Verified [ 10005 ] New: Resolved [ 5 ]

            The priority of Minor is totally wrong here. This is a terrible experience for users who are not using Confluence (or JIRA) for software development.

            A better generic message is required as a default is the minimum required but the ability to customise it is also essential.

            Trevor Campbell (Inactive) added a comment - The priority of Minor is totally wrong here. This is a terrible experience for users who are not using Confluence (or JIRA) for software development. A better generic message is required as a default is the minimum required but the ability to customise it is also essential.
            Dobroslawa Wierzbicka (Inactive) made changes -
            Description Original: h3.Problem statement

            The latest new user email read as follows:

            {quote}Subject: [Atlassian] USERNAME, welcome to Atlassian OnDemand
            Sent by: jira@planningnsw.atlassian.net

            Message: Your OnDemand account has been created! Atlassian OnDemand is the à la carte hosted development and collaboration solution for teams building great software. Log in now to track your issues and tasks, collaborate with your team, and stay on top of project activity.{quote}

            h3.Suggested solution
            1. Can this be sent by *cloud*@domain.atlassian.net rather than *jira*@domain.atlassian.net? The current sender address is particularly confusing when invited users will only use Confluence
            2. Can the message be more generic - not every OnDemand client is using it for "building great software". I've attached the old Confluence OnDemand invitation for reference.

            This causes support issues as the new user email is getting ignored or deleted by users.

            Alternatively, the ability to create a custom message template would be a better approach. We actually send out a 2nd follow up message to this invitation that also cover tips such as reminders to set their time zone, setting a default landing page, notifications and where to get more help.
            New: h3.Problem statement

            The latest new user email read as follows:

            {quote}Subject: [Atlassian] USERNAME, welcome to Atlassian OnDemand
            Sent by: jira@example.atlassian.net

            Message: Your OnDemand account has been created! Atlassian OnDemand is the à la carte hosted development and collaboration solution for teams building great software. Log in now to track your issues and tasks, collaborate with your team, and stay on top of project activity.{quote}

            - Receiving emails from _*jira*@example.atlassian.net_ can be confusing when invited users will only use Confluence.
            - This causes support issues as the new user email is getting ignored or deleted by users.

            h3.Suggested solution
            1. Can the invitation be sent from _*cloud*@example.atlassian.net_?
            2. Can the message be more generic - not every Cloud customer is using it for "building great software". I've attached the old Confluence OnDemand invitation for reference: [^confluenceinvitemessage.png].

            Ideally, the Cloud site administrators should have the ability to create a custom message template.
            We actually send out a 2nd follow up message to this invitation that also cover tips such as reminders to set their time zone, setting a default landing page, notifications and where to get more help.
            Dobroslawa Wierzbicka (Inactive) made changes -
            Description Original: The latest new user email read as follows:

            Subject: [Atlassian] USERNAME, welcome to Atlassian OnDemand
            Sent by: jira@planningnsw.atlassian.net

            Message: Your OnDemand account has been created! Atlassian OnDemand is the à la carte hosted development and collaboration solution for teams building great software. Log in now to track your issues and tasks, collaborate with your team, and stay on top of project activity."

            1. Can this be sent by ondemand@SUBDOMAIN.atlassian.net rather than jira@SUBDOMAIN.atlassian.net
            2. Can the message be more generic - not every OnDemand client is using it for "building great software". I've attached the old Confluence OnDemand invitation for reference.

            This causes support issues as the new user email is getting ignored or deleted by users.

            Alternatively, the ability to create a custom message template would be a better approach. We actually send out a 2nd follow up message to this invitation that also cover tips such as reminders to set their time zone, setting a default landing page, notifications and where to get more help.
            New: h3.Problem statement

            The latest new user email read as follows:

            {quote}Subject: [Atlassian] USERNAME, welcome to Atlassian OnDemand
            Sent by: jira@planningnsw.atlassian.net

            Message: Your OnDemand account has been created! Atlassian OnDemand is the à la carte hosted development and collaboration solution for teams building great software. Log in now to track your issues and tasks, collaborate with your team, and stay on top of project activity.{quote}

            h3.Suggested solution
            1. Can this be sent by *cloud*@domain.atlassian.net rather than *jira*@domain.atlassian.net? The current sender address is particularly confusing when invited users will only use Confluence
            2. Can the message be more generic - not every OnDemand client is using it for "building great software". I've attached the old Confluence OnDemand invitation for reference.

            This causes support issues as the new user email is getting ignored or deleted by users.

            Alternatively, the ability to create a custom message template would be a better approach. We actually send out a 2nd follow up message to this invitation that also cover tips such as reminders to set their time zone, setting a default landing page, notifications and where to get more help.

              Unassigned Unassigned
              james.dellow James Dellow
              Votes:
              9 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: