After Upgrade to servicedesk 4.0 and Jira 8 the E-Mail request settings are broken and no longer functioning
Error!
Strip quotes failed to update. Please try refreshing the page.
Error!
HTML parsing failed to update. Please try refreshing the page.
Error!
Public email comments failed to update. Please try refreshing the page.
Error!
Email customer creation failed to update. Please try refreshing the page.
Alexander,
Can you go to Versions & Licenses for your instance and let me know if your JSD license appears to be still in tact?
Do you see any errors in your browser when you load the page under Developer Tools?
Regards,
Shannon
Hello,
License is fine and Valit till 2020, it is mentioning that we use all our users at the moment which is correct.
only warnings which where there before as well ( mainly "DEPRECATED JS - Inline dialog constructor has been deprecated and will be removed in a future release. Use inline dialog" etc. )
the whole system works except for those settings and as a result it does not strip HTML signatures
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alexander,
I mentioned the Versions & Licenses page because sometimes there will be another error there; I wasn't doubting the fact that your license was valid.
The DEPRECATED JS messages are normal to see in Developer Tools.
Could you have a look at your Jira server logs after loading the page and tell us what messages are there when you load the page?
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
with the defaults:
no logs show any significance, the catalina has a filter mention when comming from the dashboard and the jira log has a mention that my user loged in as administrator.
nothing else or warnings / errors
should i enable a specific logger / level to maybe get something ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries, Alexander. When you reported the issue I found a similar problem that had just been reported in the support queue, with no solution.
This morning, I see they have created a bug ticket for it:
It appears to be visual only, and is fixed in Service Desk 4.0.1.
Let me know if you have any questions!
Regards,
Shannon
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.