Hi!
I've just installed a new instance with Jira 8.6.1 and Service Desk 4.6.1 (server). I'd like to disable the account verification email setting in a new project, but unfortunately, that setting is missing in the new instance as shown below.
In our old instance, the settings shows without any errors. The old instance is running Jira 8.5.1 and Service Desk 4.5.1. Could this be related to the different versions? The e-mail settings are configured the same way, but on different servers.
Thanks in advance!
Hello again @Adrian_Munther,
After discussing the issue with @Earl McCutcheon a bit more, I could reproduce the issue in a fresh JSW + JSD 4.6.0 installation. I could also find the cause and fix it.
I'm certain that you are running into this bug: https://jira.atlassian.com/browse/JSDSERVER-6695. The workaround is installing a missing library called "atlassian-chaperone" manually. You can download the jar file for the library and follow the instructions in the "Workaround" section of the bug report to fix the problem.
Hope this helps.
Cheers,
Elton
Please disregard this answer.
Hello @Adrian_Munther,
I couldn't reproduce this bug in a fresh 4.6.1 installation. By looking at the code, the only way I could figure out how to reproduce the issue is by disabling a feature flag.
Could you try checking if the feature flag "sd.customer.notifications.suppress.welcome.email.disabled" is enabled in your instance?
You can follow this KB page (or access <YOUR_JIRA_URL>/secure/SiteDarkFeatures!default.jspa), and look for the "sd.customer.notifications.suppress.welcome.email.disabled" flag in the list. If it is there, just click on the "Disable" next to it to remove it from the list, and refresh the "Customer notifications" page.
Hope this solves your issue.
Cheers,
Elton
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Adrian_Munther ,
Thank you for pointing this one out, and it is definitely missing from the UI and looks like a new BUG in the 4.6.X versions.
I created the following Bug Report so we can follow up on this and get a fix in place.
Please add yourself as a watcher on the bug if you would like to get updates on the status.
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.