Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-2296

As an admin I would like option to re-send an invitation email to a customer

    • We collect Jira Service Desk 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 Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Summary

      When a customer already exists in a Service Desk, if I re-invite them using an email address, nothing happens. It will be silently ignored.

      Steps to Reproduce

      1. Go to the 'Customers' page in a Service Desk
      2. Invite a customer, by clicking 'Invite', enter an email and click 'Send invites'
        • The invite will be sent
      3. Do the same process again with the same email address

      Expected Results

      Either:

      • a new invite email is send (if this process was done twice, is most likely because the first one didn't work) or warn the user that a customer with that email already exists and no email will be sent.
      • No invite is sent, but I receive a message informing me this user is already a customer, but would I like to resend the invitation to this Service Desk

      Notes

      The initial invitation containing the link to set a password will only ever be sent once, when the user is initially created. After this time, the Forgot password link can be used. Invitations to different Service Desks send a new invite email each time, and these are what can be re-sent.

          Form Name

            [JSDSERVER-2296] As an admin I would like option to re-send an invitation email to a customer

            I still get the same result: Resend Invite does not work. How to solve this?

            Nienke.hagens added a comment - I still get the same result: Resend Invite does not work. How to solve this?

            We need this functionality. Has this been added already? Thanks!

            Deleted Account (Inactive) added a comment - We need this functionality. Has this been added already? Thanks!

            One of my clients ran into this problem too. Once they invite new customers to sign up for their Service Desk and the token expires - there's only a complicated way for them to re-invite their (new) customers. Annoying for both sides. Also there's apparently no way to regulate the expiry time for the token. Why? And why does it take so much time to work on obviously reasonable requests?

            Johannes Rudolf added a comment - One of my clients ran into this problem too. Once they invite new customers to sign up for their Service Desk and the token expires - there's only a complicated way for them to re-invite their (new) customers. Annoying for both sides. Also there's apparently no way to regulate the expiry time for the token. Why? And why does it take so much time to work on obviously reasonable requests?

            Any new updates regarding this feature? 
            We need it too.

            Khai Shaun Ng added a comment - Any new updates regarding this feature?  We need it too.

            Lars Schretlen added a comment - - edited

            We work with Jira from the cloud.

            Re-send invite still doesnt work. for us.

             

            Lars Schretlen added a comment - - edited We work with Jira from the cloud. Re-send invite still doesnt work. for us.  

            I would like some way to resend the invite!

            Vanessa Plugues added a comment - I would like some way to resend the invite!

            Adam Panes added a comment - - edited

            This is super important feature, the admins have to be able resend the invitation e-mails in case the old ones are not valid anymore, or something has changed. There is no way how to achieve this right now. And this should be possible with a Bulk option as well. Now you have to compose an e-mail one by one with details of the particular user.

            And yes, this is not fixed even in JIRA 7.11 and service desk 3.14

            Adam Panes added a comment - - edited This is super important feature, the admins have to be able resend the invitation e-mails in case the old ones are not valid anymore, or something has changed. There is no way how to achieve this right now. And this should be possible with a Bulk option as well. Now you have to compose an e-mail one by one with details of the particular user. And yes, this is not fixed even in JIRA 7.11 and service desk 3.14

            This is not resolved. We are running Jira Server 7.10 with Service Desk 3.13 and have no option of re-sending user invites. This should be an easy to use option on the user management page.

            IT Services added a comment - This is not resolved. We are running Jira Server 7.10 with Service Desk 3.13 and have no option of re-sending user invites. This should be an easy to use option on the user management page.

            Since JSD Server 3.3.0 an invitation will always be sent anytime you invite a user to a Service Desk. Inviting the same user will resend the invitation.

            The only time the invitation will stop being sent, is once the user has logged into the instance once, as this implies that they have set their own password.

            From this point, inviting to Service Desks will not send an invite to that user again.

            Marking this as Done, based on the above.

            If this is not enough, would recommend commenting here, or preferably opening a new suggestions for our PMs to reconsider.

            Regards

            Matt

            JIRA Service Desk developer

            Matthew McMahon (Inactive) added a comment - Since JSD Server 3.3.0 an invitation will always be sent anytime you invite a user to a Service Desk. Inviting the same user will resend the invitation. The only time the invitation will stop being sent, is once the user has logged into the instance once, as this implies that they have set their own password. From this point, inviting to Service Desks will not send an invite to that user again. Marking this as Done, based on the above. If this is not enough, would recommend commenting here, or preferably opening a new suggestions for our PMs to reconsider. Regards Matt JIRA Service Desk developer

            As a workaround, I was able to create a query to pull a list of users from the DB with outstanding invites and generate their invite URLs from the information in the DB.

            NOTE:

            • This query was written for Postgres and is provided as-is and not supported by Atlassian
            • As with any database manipulation backup before you query or use a read-only user, this is simply a select, but could affect performance on large instances
            • The query does not generate a new invite, so if the invite has already expired the link will not work for the user
            SELECT
                u.id,
                u.user_name,
                u.email_address,
                pr.name AS role,
                p.pname AS project,
                p.pkey AS project_key,
                (SELECT
                     ps.propertyvalue
                   FROM
                     propertyentry pe
                   JOIN
                     propertystring ps ON ps.id = pe.id AND pe.property_key = 'jira.baseurl')
                || '/servicedesk/customer/portal/'
                || sd_project."ID"
                || '/user/visitportal?username='
                || u.lower_user_name
                || '&token='
                || 
                    SUBSTRING(ua_invite.attribute_value
                    FROM position('":"' IN ua_invite.attribute_value) + 3
                    FOR (char_length(ua_invite.attribute_value) - position('","' IN ua_invite.attribute_value) - 5)
                 )
                 || '&sda_source=notification-email' AS invite_URL
                
            FROM
                cwd_user u
            JOIN
                projectroleactor pra ON pra.roletypeparameter = u.lower_user_name AND pra.roletype = 'atlassian-user-role-actor'
            JOIN
                projectrole pr ON pr.id = pra.projectroleid AND pr.name = 'Service Desk Customers'
            JOIN
                project p ON p.id = pra.pid
            JOIN
                "AO_54307E_SERVICEDESK" sd_project ON sd_project."PROJECT_ID" = p.id
            JOIN
                cwd_user_attributes ua_invite ON ua_invite.user_id = u.id AND ua_invite.attribute_name = 'local.servicedesk.outstanding.agent.invites'
            

            Douglas McMorris (Inactive) added a comment - - edited As a workaround, I was able to create a query to pull a list of users from the DB with outstanding invites and generate their invite URLs from the information in the DB. NOTE: This query was written for Postgres and is provided as-is and not supported by Atlassian As with any database manipulation backup before you query or use a read-only user, this is simply a select, but could affect performance on large instances The query does not generate a new invite, so if the invite has already expired the link will not work for the user SELECT u.id, u.user_name, u.email_address, pr.name AS role, p.pname AS project, p.pkey AS project_key, (SELECT ps.propertyvalue FROM propertyentry pe JOIN propertystring ps ON ps.id = pe.id AND pe.property_key = 'jira.baseurl' ) || '/servicedesk/customer/portal/' || sd_project. "ID" || '/user/visitportal?username=' || u.lower_user_name || '&token=' || SUBSTRING(ua_invite.attribute_value FROM position( ' ":" ' IN ua_invite.attribute_value) + 3 FOR (char_length(ua_invite.attribute_value) - position( ' "," ' IN ua_invite.attribute_value) - 5) ) || '&sda_source=notification-email' AS invite_URL FROM cwd_user u JOIN projectroleactor pra ON pra.roletypeparameter = u.lower_user_name AND pra.roletype = 'atlassian-user-role-actor' JOIN projectrole pr ON pr.id = pra.projectroleid AND pr.name = 'Service Desk Customers' JOIN project p ON p.id = pra.pid JOIN "AO_54307E_SERVICEDESK" sd_project ON sd_project. "PROJECT_ID" = p.id JOIN cwd_user_attributes ua_invite ON ua_invite.user_id = u.id AND ua_invite.attribute_name = 'local.servicedesk.outstanding.agent.invites'

              Unassigned Unassigned
              jsilveira Jaime S
              Votes:
              15 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: