• 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.

      Atlassian status update as of 15th January 2018

      Hi all,

      Good news - The ability to disable welcome email is now available in Jira Service Desk version 3.10.
      To find out more about this fix, check out our release notes here.

      On behalf of the JSD team, I want to thank all of you for contributing to this ticket. Your patience and feedback have shaped this enhancement.

      Cheers,

      Vidhu Sharma
      Product Manager - Jira Service Desk

      Atlassian update as of 23rd May 2017

      Hi all,

      Thanks for your feedback on this. We are aware that this is important and understand that the account activation email is causing confusion for your customers. 

      Welcome emails are instance wide and span across multiple projects, which is why modifying them is challenging. We are now exploring the possibility of suppressing these emails and building a new flow for users to activate accounts.

      Once again, thanks for voicing your concerns and stay tuned for future updates. 

      Cheers,

      JIRA Service Desk Team

       


      Problem Definition

      Due to reduce the number of communication between JIRA and users, some administrators would like to disable the Welcome messages

      • Welcome messages are also referred to as "Activate Your Account" emails

      Suggested Solution

      Add the new customer welcome message as a notification type that can be edited within the notification scheme.

      Example Use Case

      "We are running into a problem with JIRA service desk whereby we need to allow for open customer enrollment, but we do not support a portal site and do not want to link customers to that site in their update emails. The entire Welcome email is entirely unnecessary for this reason, and while we can use the default JIRA notifications as a way to update customers, we would like to be able to just change the outgoing emails from Service Desk the same as with JIRA notifications. "

        1. custom mail handler for jsd.png
          130 kB
        2. image-2017-09-28-16-10-05-064.png
          14 kB
        3. image-2017-09-29-14-52-20-775.png
          6 kB
        4. image-2018-02-12-16-52-26-272.png
          image-2018-02-12-16-52-26-272.png
          134 kB
        5. image-2018-02-12-19-41-23-958.png
          image-2018-02-12-19-41-23-958.png
          13 kB
        6. image-2018-02-27-12-40-29-280.png
          image-2018-02-27-12-40-29-280.png
          202 kB
        7. o365_2.png
          5 kB
        8. o365.png
          113 kB
        9. print.png
          print.png
          8 kB
        10. print.png
          print.png
          30 kB

            [JSDSERVER-1708] Provide ability to disable the welcome email to new customers

            Perbility added a comment -

            It's not complicated at all to never ever send a welcome mail.

            We don't need special handling of SD users, we're find if noone gets one.

            Perbility added a comment - It's not complicated at all to never ever send a welcome mail. We don't need special handling of SD users, we're find if noone gets one.

            @Vidhu Sharma:  we're running 3.12, and despite setting "Account verification email" to Off, first-time emailers STILL get a notification "[JIRA] Aktivieren Sie Ihr Konto". See also support request SDS-33698 for more info.

            Marco Schuster added a comment - @Vidhu Sharma:  we're running 3.12, and despite setting "Account verification email" to Off, first-time emailers STILL get a notification " [JIRA] Aktivieren Sie Ihr Konto". See also support request SDS-33698 for more info.

            Hi nicholas41 - This improvement was implemented in Jira Service Desk 3.10. Release notes here can help you turn off verification emails, if you are using the above recommended version or higher (for Jira Service Desk on a supported Jira version).

            Thank you.

            V (Inactive) added a comment - Hi nicholas41 - This improvement was implemented in Jira Service Desk 3.10.  Release notes here  can help you turn off verification emails, if you are using the above recommended version or higher (for Jira Service Desk on a supported Jira version). Thank you.

            Nicholas Kuün added a comment - - edited

            JIRA v7.3.7 here.

            NO option to disable the activation/welcome email.

            Chaps, this is really a poor show. It cannot be difficult to code this option in.

            Nicholas Kuün added a comment - - edited JIRA v7.3.7 here. NO option to disable the activation/welcome email. Chaps, this is really a poor show. It cannot be difficult to code this option in.

            Thank you but the feature is still not implemented

            Deleted Account (Inactive) added a comment - Thank you but the feature is still not implemented

            Hi nahmadi,

            Here's the link to the feature request for customization: https://jira.atlassian.com/browse/JSDSERVER-1386

            Keri Duthie (Inactive) added a comment - Hi nahmadi , Here's the link to the feature request for customization: https://jira.atlassian.com/browse/JSDSERVER-1386

            I don't see an option to edit the email. Please point me to the right documentation . Why was this issue closed when it only handles one portion of the request? 

            Deleted Account (Inactive) added a comment - - edited I don't see an option to edit the email. Please point me to the right documentation . Why was this issue closed when it only handles one portion of the request? 

            Thanks

            Jérémie added a comment - Thanks

            Lachlan G (Inactive) added a comment - - edited

            it2108346646 jeremie2 I've created a bug ticket to track that problem. Please follow that ticket for updates https://jira.atlassian.com/browse/JSDSERVER-5713

            -Jira Service Desk Team

            Lachlan G (Inactive) added a comment - - edited it2108346646 jeremie2 I've created a bug ticket to track that problem. Please follow that ticket for updates https://jira.atlassian.com/browse/JSDSERVER-5713 -Jira Service Desk Team

            WEI IT added a comment -

            this problem (as above) persists with JIRA Service Desk 3.11.0 and JIRA Software 7.8.0

            WEI IT added a comment - this problem ( as above ) persists with JIRA Service Desk 3.11.0 and JIRA Software 7.8.0

            Jérémie added a comment - - edited

            @WEI IT Same issue here with firefox, my Jira is behind an nginx https reverse proxy too

            It would be great if someone could told us how to disable this in a manual way ? Maybe  by editing a config file or in database

            Jérémie added a comment - - edited @WEI IT Same issue here with firefox, my Jira is behind an nginx https reverse proxy too It would be great if someone could told us how to disable this in a manual way ? Maybe  by editing a config file or in database

            Oded Ron added a comment -

            Hi,

            I do not have the option to check this box and stop these notifications:

            What am I missing here??

             

            Oded

            Oded Ron added a comment - Hi, I do not have the option to check this box and stop these notifications: What am I missing here??   Oded

            WEI IT added a comment - - edited

            i'm having a problem where the "do not send account verification emails" toggle will not stay checked "green"

            as it stands, this means i can't actually disable the invite confirmation emails

            we're running an eval of Jira software and core 7.7.2, and service desk 3.10.2, currently just on the h2 db

            if i pull up google chrome's javascript console and click the toggle, the following is shown:

            POST https://jira.MY.FQDN/rest/servicedesk/notifications/1/customerinvite/34 409 ()
            (anonymous)
            XMLHttpRequest.send	@	batch.js?agile_globa…erational=true:7006
            send	@	batch.js:200
            ajax	@	batch.js:194
            value	@	context-sd.admin.out…6.js?locale=en-US:1
            value	@	context-sd.admin.out…6.js?locale=en-US:1
            update	@	context-sd.admin.out…6.js?locale=en-US:1
            value	@	context-sd.admin.out…6.js?locale=en-US:1
            change #js-suppress-customer-invite-email	@	context-sd.admin.out…6.js?locale=en-US:1
            dispatch	@	batch.js:107
            h	@	batch.js:99
            
            Uncaught TypeError: t.forEach is not a function
                at Object.<anonymous> (context-sd.admin.out…6.js?locale=en-US:1)
                at j (batch.js:63)
                at Object.fireWith (batch.js:64)
                at Object.fire [as reject] (batch.js:64)
                at Object.<anonymous> (context-sd.admin.out…6.js?locale=en-US:1)
                at j (batch.js:63)
                at Object.fireWith [as rejectWith] (batch.js:64)
                at d (batch.js:189)
                at XMLHttpRequest.b (batch.js:201)
            

            has anyone else had this issue or similar?

            cc: @vsharma

            —

            edit: maybe i should note, this is running behind nginx for https

            WEI IT added a comment - - edited i'm having a problem where the "do not send account verification emails" toggle will not stay checked "green" as it stands, this means i can't actually disable the invite confirmation emails we're running an eval of Jira software and core 7.7.2, and service desk 3.10.2, currently just on the h2 db if i pull up google chrome's javascript console and click the toggle, the following is shown: POST https: //jira.MY.FQDN/rest/servicedesk/notifications/1/customerinvite/34 409 () (anonymous) XMLHttpRequest.send @ batch.js?agile_globa…erational= true :7006 send @ batch.js:200 ajax @ batch.js:194 value @ context-sd.admin.out…6.js?locale=en-US:1 value @ context-sd.admin.out…6.js?locale=en-US:1 update @ context-sd.admin.out…6.js?locale=en-US:1 value @ context-sd.admin.out…6.js?locale=en-US:1 change #js-suppress-customer-invite-email @ context-sd.admin.out…6.js?locale=en-US:1 dispatch @ batch.js:107 h @ batch.js:99 Uncaught TypeError: t.forEach is not a function at Object .<anonymous> (context-sd.admin.out…6.js?locale=en-US:1) at j (batch.js:63) at Object .fireWith (batch.js:64) at Object .fire [as reject] (batch.js:64) at Object .<anonymous> (context-sd.admin.out…6.js?locale=en-US:1) at j (batch.js:63) at Object .fireWith [as rejectWith] (batch.js:64) at d (batch.js:189) at XMLHttpRequest.b (batch.js:201) has anyone else had this issue or similar? cc: @vsharma — edit: maybe i should note, this is running behind nginx for https

            @Ivan: Ok, thanks - that's where I was confused. "Account verification" sounds kind of different than "Welcome E-Mail"

            catenoJanWerner added a comment - @Ivan: Ok, thanks - that's where I was confused. "Account verification" sounds kind of different than "Welcome E-Mail"

            @Jan Werner:

            Ivan Tovbin added a comment - @Jan Werner:

            @Ivan: Thanks, but that's where I've been loking. This is what's available in my JSD project

            Which of these will disable welcome email to new customers? Or is this the same as "Account verification email"?

            catenoJanWerner added a comment - @Ivan: Thanks, but that's where I've been loking. This is what's available in my JSD project Which of these will disable welcome email to new customers? Or is this the same as "Account verification email"?

            @Jan Werner

            Project Settings -> Customer Notifications

            Ivan Tovbin added a comment - @Jan Werner Project Settings -> Customer Notifications

            Hi @Atlassian,

            maybe I'm blind, but have no idea where to find this option. In JSD 3.10 Release notes, it just says "Customize/Disable Welcome E-Mail to New Customers" and there's a link to this issue. Some information how this was implemented would be really nice.

            Thanks,
            Jan

            catenoJanWerner added a comment - Hi @Atlassian, maybe I'm blind, but have no idea where to find this option. In JSD 3.10 Release notes, it just says "Customize/Disable Welcome E-Mail to New Customers" and there's a link to this issue. Some information how this was implemented would be really nice. Thanks, Jan

            Everyone watching and voting for this issue.  I was voting on this issue for the customization (not the disable portion).  So please move your votes over to JSDSERVER-1386

            It has only 75 votes and needs a lot more. 

             

            Susan Hauth [Jira Queen] added a comment - Everyone watching and voting for this issue.  I was voting on this issue for the customization (not the disable portion).  So please move your votes over to JSDSERVER-1386 It has only 75 votes and needs a lot more.   

            Kevin Decker added a comment - - edited

            Duplicated comment

            Kevin Decker added a comment - - edited Duplicated comment

            Vidhu - is there any movement on being able to customize the Welcome messaging? 

            Kevin Decker added a comment - Vidhu - is there any movement on being able to customize the Welcome messaging? 

            Hi all,

            Good news - The ability to disable welcome email is now available in Jira Service Desk version 3.10.
            To find out more about this fix, check out our release notes here.

            On behalf of the JSD team, I want to thank all of you for contributing to this ticket. Your patience and feedback have shaped this enhancement.

            Cheers,

            Vidhu Sharma
            Product Manager - Jira Service Desk

            V (Inactive) added a comment - Hi all, Good news - The ability to disable welcome email is now available in Jira Service Desk version 3.10. To find out more about this fix, check out our release notes  here . On behalf of the JSD team, I want to thank all of you for contributing to this ticket. Your patience and feedback have shaped this enhancement. Cheers, Vidhu Sharma Product Manager - Jira Service Desk

            hi @tarahall we are using a secure tunnel work around now with the portal working.

            philip cooper added a comment - hi @tarahall we are using a secure tunnel work around now with the portal working.

            jirajester added a comment -

            @pcooper which jar do you need?

            jirajester added a comment - @pcooper which jar do you need?

            Hi Guys

            We have found a work around because of the silence from @Atlassian @jirasupport

             

            We have created a secure tunnel to localhost using ngrok.com.

             

            This means we can use all the features of JSD.

             

            Philip

             

             

             

             

             

             

            philip cooper added a comment - Hi Guys We have found a work around because of the silence from @Atlassian @jirasupport   We have created a secure tunnel to localhost using ngrok.com.   This means we can use all the features of JSD.   Philip            

            @pcooper703996344 now I'm testing Freshdesk and its flexible. The first task I did - disabled "Welcome e-mail"

            Deleted Account (Inactive) added a comment - @ pcooper703996344 now I'm testing Freshdesk and its flexible. The first task I did - disabled "Welcome e-mail"

            @tarahall im a total Java novice do you have working jar files i can download?

             

            philip cooper added a comment - @tarahall im a total Java novice do you have working jar files i can download?  

            Mika Varis added a comment -

            What alternative systems are you guys using?

            Mika Varis added a comment - What alternative systems are you guys using?

            FYI @jira_support after waiting for 2 years for this to change, we moved back to out old support platform. 

            Yaron Kufert added a comment - FYI @jira_support after waiting for 2 years for this to change, we moved back to out old support platform. 

            Hi @jira_support is there any update on this?

            philip cooper added a comment - Hi @jira_support is there any update on this?

            Because of zero updates from Jira we are on our way to the new, more flexible helpdesk system

            Deleted Account (Inactive) added a comment - Because of zero updates from Jira we are on our way to the new, more flexible helpdesk system

            Please share your workaround steps with this issue. Thank you!

            Deleted Account (Inactive) added a comment - - edited Please share your workaround steps with this issue. Thank you!

            jirajester added a comment -

            I'd do a grep for it from your $JIRA_HOME/

            grep -Ri notification.activate.your.account *
            

            jirajester added a comment - I'd do a grep for it from your $JIRA_HOME/ grep -Ri notification.activate.your.account *

            I am using Swedish language pack and I cannot find a corresponding sd--i18n_se_SE for Swedish in my jira-servicedesk-application-3.8.1

            The language pack is installed as a plugin so maybe this is the reason of it not showing up here so I tried checking jira-software-language-pack-sv_SE... but I find no file similar like i18n/sd-i18n.properties here either

            Any suggestions?

             

            Christoffer added a comment - I am using Swedish language pack and I cannot find a corresponding sd--i18n_ se_SE for Swedish in my jira-servicedesk-application-3.8.1 The language pack is installed as a plugin so maybe this is the reason of it not showing up here so I tried checking jira-software-language-pack-sv_SE... but I find no file similar like i18n/sd-i18n.properties here either Any suggestions?  

            jirajester added a comment -

            use my hack until it's available to us all

            jirajester added a comment - use my hack until it's available to us all

            An ETA for JSDSERVER would be really nice. We are selling a new Product for end customer market. And we' ll have a lot of confused customers, because we use JSD in this project for external E-Mail Support only.

            Please keep us up to date, 

            Stefan Auer added a comment - An ETA for JSDSERVER would be really nice. We are selling a new Product for end customer market. And we' ll have a lot of confused customers, because we use JSD in this project for external E-Mail Support only. Please keep us up to date, 

            This feature has just been made available in Cloud. Any ETA for Server?

            Ivan Tovbin added a comment - This feature has just been made available in Cloud. Any ETA for Server?

            Thought that this is a ticket system and not a blog or chat

            Thomas Radigewski added a comment - Thought that this is a ticket system and not a blog or chat

            jirajester added a comment -

            here are the commands i used to open and pack the .jar on my jump box

            unpack:
            jar xvf jira-servicedesk-3.5.0-REL-0008.jar
            pack:
            jar cvf jira-servicedesk-3.5.0-REL-0008.jar *
            

            make sure to move the .jar out of the dir before packing also

            jirajester added a comment - here are the commands i used to open and pack the .jar on my jump box unpack: jar xvf jira-servicedesk-3.5.0-REL-0008.jar pack: jar cvf jira-servicedesk-3.5.0-REL-0008.jar * make sure to move the .jar out of the dir before packing also

            CPC added a comment - - edited

            looks like my SELinux permissions changed on the file. Let me see if setting them to what the others are set to fixes it. 

             

            Update: That seems to have worked. Sorry for the false alarm

            CPC added a comment - - edited looks like my SELinux permissions changed on the file. Let me see if setting them to what the others are set to fixes it.    Update: That seems to have worked. Sorry for the false alarm

            CPC added a comment -

            I did make a backup. Tried restoring it and it won't even start up (permissions are the way they were). I used VIM to open up the jar file and select the item to update....I then :x the file and :x out of the jar. 

            CPC added a comment - I did make a backup. Tried restoring it and it won't even start up (permissions are the way they were). I used VIM to open up the jar file and select the item to update....I then :x the file and :x out of the jar. 

            jirajester added a comment - - edited

            did you open the .jar somewhere else, then repack it and deploy it?
            Also, make sure files are owned by JIRA before packing it back up into the .jar

             

            and make backups!

            jirajester added a comment - - edited did you open the .jar somewhere else, then repack it and deploy it? Also, make sure files are owned by JIRA before packing it back up into the .jar   and make backups!

            CPC added a comment - - edited

            I modified the properties file to make the email say what i wanted. I then restarted JIRA successfully. However, now I get 0 tabs on the left side when i go into my service desk!!

             It seems to be under the impression that this project is brand new!!! I had made a LOT of changes to this project...please tell me I didn't lose all of them

            CPC added a comment - - edited I modified the properties file to make the email say what i wanted. I then restarted JIRA successfully. However, now I get 0 tabs on the left side when i go into my service desk!!  It seems to be under the impression that this project is brand new!!! I had made a LOT of changes to this project...please tell me I didn't lose all of them

            CPC added a comment -

            Thank you

            CPC added a comment - Thank you

            jirajester added a comment -

            as root, try this

            cd /
            find . -type f -name jira-servicedesk-*.jar

            jirajester added a comment - as root, try this cd / find . -type f -name jira-servicedesk-*.jar

            CPC added a comment -

            Sadly I can't seem to find the Jar file in the locations provided. My install folder is /opt/atlassian/Jira/....where underneath there can i find it?

            CPC added a comment - Sadly I can't seem to find the Jar file in the locations provided. My install folder is /opt/atlassian/Jira/....where underneath there can i find it?

            jirajester added a comment -

            edit the files i noted above in the .jar then redeploy - so far it's working for us

            jirajester added a comment - edit the files i noted above in the .jar then redeploy - so far it's working for us

            CPC added a comment -

            I am also having this issue. All I want is to be able to change the welcome message so its not so ridiculous but its getting sent out automatically and I have no options to change it. Is there a workaround I can use in the mean time?

            CPC added a comment - I am also having this issue. All I want is to be able to change the welcome message so its not so ridiculous but its getting sent out automatically and I have no options to change it. Is there a workaround I can use in the mean time?

            jirajester added a comment -

            Looks good - deploying to prod tonight!

            jirajester added a comment - Looks good - deploying to prod tonight!

            jirajester added a comment - - edited

            So... was able to successfully allow external customer to create an issue from an email without getting any notifications

            after modifying the files and restarting - created internal account with the email for everything - no password, then added that user to the project "Service Desk Customer" Role

            so far, no notifications in my test email account and tickets are being created!

            Only thing - have to delete messages that are not being sent in the mail queue

            jirajester added a comment - - edited So... was able to successfully allow external customer to create an issue from an email without getting any notifications after modifying the files and restarting - created internal account with the email for everything - no password, then added that user to the project "Service Desk Customer" Role so far, no notifications in my test email account and tickets are being created! Only thing - have to delete messages that are not being sent in the mail queue

            I am an external customer of JIRA, but am getting all of these internal development comments.  Not sure this is what you intended?

            Jennifer Dumont added a comment - I am an external customer of JIRA, but am getting all of these internal development comments.  Not sure this is what you intended?

            jirajester added a comment - - edited

            0 emails sent! but, "customer email" did not create a ticket from and email request

            internal emails worked (users with account and license)

            1/2 way there?

            jirajester added a comment - - edited 0 emails sent! but, "customer email" did not create a ticket from and email request internal emails worked (users with account and license) 1/2 way there?

            jirajester added a comment -

            dev system test

            from /opt/atlassian/jira/atlassian-jira/WEB-INF/application-installation/jira-servicedesk-application/jira-servicedesk-3.5.0-REL-0008.jar

            opened up .jar

            vi i18n/sd-i18n.properties

            commented out

            ###################
            # ~CUSTOMER LOGIN #
            ###################
            #cv.login.title=Login
            #cv.login.username=Username
            #cv.login.password=Password
            #cv.login.forgotten.password=Forgot your password?
            #cv.login.captcha.label=Please enter the word as shown below
            #cv.login.captcha.refresh=Refresh the image
            #cv.login.submit.label=Log in
            #cv.login.remember.me=Keep me logged in
            #cv.login.stay.logged.in=Stay logged in
            #cv.login.pub.signup.title=Don''t have a login?
            #cv.login.pub.signup.desc=Sign up for an account to raise and comment on requests
            #cv.login.pub.create.account=Sign up for an account
            #cv.login.pub.need.account=Need an account?
            #cv.login.pub.signup.link=Sign up
            #cv.login.signup.not.public=Not a member? To request an account, please contact your JIRA administrators.
            
            #cv.forgotpassword.page.title=Forgot password
            #cv.forgotpassword.title=Forgot password
            #cv.forgotpassword.submit.label=Email me
            #cv.forgotpassword.back.to.login=Back to login
            #cv.forgotpassword.success.title=Access reset password link
            #cv.forgotpassword.success.line1=A reset password link has been sent to the specified email address. Follow the link to select a new password.
            #cv.forgotpassword.success.line2=If you did not receive a reset password link, request one by entering your user account details.
            #cv.forgotpassword.disable=This instance does not support password reset.
            #cv.resetpassword.page.title=Create New Password
            #cv.resetpassword.title=Create new Password
            #cv.resetpassword.current.password=Current Password
            #cv.resetpassword.new.password=New Password
            #cv.resetpassword.confirm.password=Confirm Password
            #cv.resetpassword.error.confirm=Password does not match. You must type the same password.
            #cv.resetpassword.submit.title=Ctrl+Alt+s to submit this form
            
            #cv.setpassword.page.title=Set New Password
            #cv.setpassword.form.title=Welcome to {0}!
            #cv.setpassword.form.welcome=You are almost there - we just need to grab a password so you can login later.
            #cv.setpassword.form.label.username=Username
            #cv.setpassword.form.label.email=Email
            #cv.setpassword.form.label.password=Password
            #cv.setpassword.form.label.confirm=Confirm
            #cv.setpassword.form.label.fullname=Full name
            #cv.setpassword.form.label.show.password=Show password
            #3cv.setpassword.form.button.save.and.continue=Save and continue
            #cv.setpassword.form.error.blank.password=Password must not be blank
            #cv.setpassword.form.error.blank.fullname=Full name must not be blank
            #cv.setpassword.form.error.fullname.exceed.max.length=Full name must be less than 255 character
            
            
            #####################
            # ~CUSTOMER PROFILE #
            #####################
            #cv.profile.you.can=You can
            #cv.profile.log.in.with=Log in with
            #cv.profile.log.in=Log in
            #cv.profile.timezone=Time zone
            #cv.profile.change.password=Change password
            #cv.profile.send.notifications.to=Send notifications to
            #cv.profile.edit.your.profile=Edit your profile
            #cv.profile.readonly=You cannot edit your name, password or email address because they are stored in a read-only user directory.
            #cv.profile.error.name.empty=Name must not be empty
            #cv.profile.error.name.too.long=Name must be less than 255 characters long
            #cv.profile.error.email.empty=Email must not be empty
            #cv.profile.error.email.too.long=Email must be less than 255 characters long
            #cv.profile.error.email.invalid=Email address is invalid
            #cv.profile.error.languageKey.invalid=Language is invalid
            #cv.profile.changepassword.current.none.error=You must type your current password
            #cv.profile.changepassword.current.incorrect.error=Password is incorrect
            #cv.profile.changepassword.new.none.error=You must specify a new password
            #cv.profile.changepassword.confirm.none.error=You must re-type the new password
            #cv.profile.changepassword.confirm.incorrect.error=Passwords do not match
            #cv.profile.changepassword.logout.warning=You''ll be asked to log in again after you update your password.
            #cv.profile.change.avatar=Change avatar
            #cv.profile.change.avatar.gravatar=Change your avatar at
            #cv.profile.avatar.accessibility.text=Profile avatar
            #cv.profile.atlassianid.managed=Your profile is managed by Atlassian account. You can edit your name, password and avatar in Atlassian account, but your email address cannot be changed.
            #cv.profile.atlassianid.account.settings.updated.success=Atlassian account account settings updated successfully
            #cv.profile.atlassianid.account.settings.updated.success.note=If you updated your name, the change will be shown on your next login.
            #cv.profile.atlassianid.account.settings.updated.failure=Atlassian account account settings update failed
            #cv.profile.atlassianid.avatar.updated.success=Atlassian account avatar updated successfully
            #cv.profile.atlassianid.avatar.updated.failure=Atlassian account avatar update failed
            #cv.profile.atlassianid.password.updated.success=Atlassian account password updated successfully
            #cv.profile.atlassianid.password.updated.failure=Atlassian account password update failed
            #cv.profile.atlassianid.fallback.updated.success=Atlassian account updated successfully
            #cv.profile.atlassianid.fallback.updated.failure=Atlassian account update failed
            
            #####################
            # ~CUSTOMER SIGN UP #
            #####################
            #cv.signup.page.title=Sign up for an account
            #cv.signup.page.full.name=Full name
            #cv.signup.page.email=Email
            #cv.signup.page.password=Password
            #cv.signup.page.confirm.password=Confirm password
            #cv.signup.page.sign.up=Sign Up
            #cv.signup.page.back.to.login=Back to login
            #cv.signup.page.show.password=Show password
            
            # Error
            #cv.signup.error.email.used=An account already exists for this email
            #cv.signup.error.not.allowed=Signup is not currently available
            #cv.signup.error.failed.to.remove.user=Failed to remove temporary user
            #cv.signup.error.input.fields=There are few errors with input values
            #cv.signup.error.jira.input.fields=There are few errors with input values
            #cv.signup.error.jira.password.required=You must specify a password.
            #cv.signup.error.blank.password=You must specify non-blank password
            #cv.signup.error.captcha.doesnt.match=Please enter the correct CAPTCHA
            #cv.signup.error.unable.to.set.property=Unable to set property to user properly
            
            

            testing after restart

            jirajester added a comment - dev system test from /opt/atlassian/jira/atlassian-jira/WEB-INF/application-installation/jira-servicedesk-application/jira-servicedesk-3.5.0-REL-0008.jar opened up .jar vi i18n/sd-i18n.properties commented out ################### # ~CUSTOMER LOGIN # ################### #cv.login.title=Login #cv.login.username=Username #cv.login.password=Password #cv.login.forgotten.password=Forgot your password? #cv.login.captcha.label=Please enter the word as shown below #cv.login.captcha.refresh=Refresh the image #cv.login.submit.label=Log in #cv.login.remember.me=Keep me logged in #cv.login.stay.logged.in=Stay logged in #cv.login.pub.signup.title=Don''t have a login? #cv.login.pub.signup.desc=Sign up for an account to raise and comment on requests #cv.login.pub.create.account=Sign up for an account #cv.login.pub.need.account=Need an account? #cv.login.pub.signup.link=Sign up #cv.login.signup.not. public =Not a member? To request an account, please contact your JIRA administrators. #cv.forgotpassword.page.title=Forgot password #cv.forgotpassword.title=Forgot password #cv.forgotpassword.submit.label=Email me #cv.forgotpassword.back.to.login=Back to login #cv.forgotpassword.success.title=Access reset password link #cv.forgotpassword.success.line1=A reset password link has been sent to the specified email address. Follow the link to select a new password. #cv.forgotpassword.success.line2=If you did not receive a reset password link, request one by entering your user account details. #cv.forgotpassword.disable=This instance does not support password reset. #cv.resetpassword.page.title=Create New Password #cv.resetpassword.title=Create new Password #cv.resetpassword.current.password=Current Password #cv.resetpassword. new .password=New Password #cv.resetpassword.confirm.password=Confirm Password #cv.resetpassword.error.confirm=Password does not match. You must type the same password. #cv.resetpassword.submit.title=Ctrl+Alt+s to submit this form #cv.setpassword.page.title=Set New Password #cv.setpassword.form.title=Welcome to {0}! #cv.setpassword.form.welcome=You are almost there - we just need to grab a password so you can login later. #cv.setpassword.form.label.username=Username #cv.setpassword.form.label.email=Email #cv.setpassword.form.label.password=Password #cv.setpassword.form.label.confirm=Confirm #cv.setpassword.form.label.fullname=Full name #cv.setpassword.form.label.show.password=Show password #3cv.setpassword.form.button.save.and. continue =Save and continue #cv.setpassword.form.error.blank.password=Password must not be blank #cv.setpassword.form.error.blank.fullname=Full name must not be blank #cv.setpassword.form.error.fullname.exceed.max.length=Full name must be less than 255 character ##################### # ~CUSTOMER PROFILE # ##################### #cv.profile.you.can=You can #cv.profile.log.in.with=Log in with #cv.profile.log.in=Log in #cv.profile.timezone=Time zone #cv.profile.change.password=Change password #cv.profile.send.notifications.to=Send notifications to #cv.profile.edit.your.profile=Edit your profile #cv.profile.readonly=You cannot edit your name, password or email address because they are stored in a read-only user directory. #cv.profile.error.name.empty=Name must not be empty #cv.profile.error.name.too. long =Name must be less than 255 characters long #cv.profile.error.email.empty=Email must not be empty #cv.profile.error.email.too. long =Email must be less than 255 characters long #cv.profile.error.email.invalid=Email address is invalid #cv.profile.error.languageKey.invalid=Language is invalid #cv.profile.changepassword.current.none.error=You must type your current password #cv.profile.changepassword.current.incorrect.error=Password is incorrect #cv.profile.changepassword. new .none.error=You must specify a new password #cv.profile.changepassword.confirm.none.error=You must re-type the new password #cv.profile.changepassword.confirm.incorrect.error=Passwords do not match #cv.profile.changepassword.logout.warning=You''ll be asked to log in again after you update your password. #cv.profile.change.avatar=Change avatar #cv.profile.change.avatar.gravatar=Change your avatar at #cv.profile.avatar.accessibility.text=Profile avatar #cv.profile.atlassianid.managed=Your profile is managed by Atlassian account. You can edit your name, password and avatar in Atlassian account, but your email address cannot be changed. #cv.profile.atlassianid.account.settings.updated.success=Atlassian account account settings updated successfully #cv.profile.atlassianid.account.settings.updated.success.note=If you updated your name, the change will be shown on your next login. #cv.profile.atlassianid.account.settings.updated.failure=Atlassian account account settings update failed #cv.profile.atlassianid.avatar.updated.success=Atlassian account avatar updated successfully #cv.profile.atlassianid.avatar.updated.failure=Atlassian account avatar update failed #cv.profile.atlassianid.password.updated.success=Atlassian account password updated successfully #cv.profile.atlassianid.password.updated.failure=Atlassian account password update failed #cv.profile.atlassianid.fallback.updated.success=Atlassian account updated successfully #cv.profile.atlassianid.fallback.updated.failure=Atlassian account update failed ##################### # ~CUSTOMER SIGN UP # ##################### #cv.signup.page.title=Sign up for an account #cv.signup.page.full.name=Full name #cv.signup.page.email=Email #cv.signup.page.password=Password #cv.signup.page.confirm.password=Confirm password #cv.signup.page.sign.up=Sign Up #cv.signup.page.back.to.login=Back to login #cv.signup.page.show.password=Show password # Error #cv.signup.error.email.used=An account already exists for this email #cv.signup.error.not.allowed=Signup is not currently available #cv.signup.error.failed.to.remove.user=Failed to remove temporary user #cv.signup.error.input.fields=There are few errors with input values #cv.signup.error.jira.input.fields=There are few errors with input values #cv.signup.error.jira.password.required=You must specify a password. #cv.signup.error.blank.password=You must specify non-blank password #cv.signup.error.captcha.doesnt.match=Please enter the correct CAPTCHA #cv.signup.error.unable.to.set.property=Unable to set property to user properly testing after restart

            This functionality would also be very important to us. JIRA ServiceDesk would principally be the perfect tool for us to use (we already use jira/confluence/bitbucket), but this is a potential dealbreaker.

            Christoph Enzinger added a comment - This functionality would also be very important to us. JIRA ServiceDesk would principally be the perfect tool for us to use (we already use jira/confluence/bitbucket), but this is a potential dealbreaker.

            jirajester added a comment - - edited

            so, the next question is - if i delete just that block, will it stop the welcome email and not break anything else? will need to test in QA env

            jirajester added a comment - - edited so, the next question is - if i delete just that block, will it stop the welcome email and not break anything else? will need to test in QA env

            Damian Wheeler (Otago) added a comment - - edited

            Hi Claus,

            for English I think Tara is correct. It the jira-servicedesk-<version>-REL*.jar which seems to have the default values.

            Damian Wheeler (Otago) added a comment - - edited Hi Claus, for English I think Tara is correct. It the jira-servicedesk-<version>-REL*.jar which seems to have the default values.

            Claus Böhmer added a comment - - edited

            Tara Hall: Not exactly. Please try this jar-file: jira-servicedesk-application**

            Claus Böhmer added a comment - - edited Tara Hall: Not exactly. Please try this jar-file: jira-servicedesk-application**

            This is extremely important and really a show stopper for us to use JSD since we have a server version which we don't expose publicly. Hence emails to customers with link which they actually cannot access is very confusing for our customers.

            Dinesh Pandey added a comment - This is extremely important and really a show stopper for us to use JSD since we have a server version which we don't expose publicly. Hence emails to customers with link which they actually cannot access is very confusing for our customers.

              Unassigned Unassigned
              f4cb44bb0fa1 Jon Burns
              Votes:
              543 Vote for this issue
              Watchers:
              294 Start watching this issue

                Created:
                Updated:
                Resolved: