Jira 8.13 causes GUI issues with dropdown menus in Customer Portals. With all browsers, the dropdowns don't appear / appear incorrectly. Is this a known issue? We have yet to try SAFE MODE to iron out possible plugin issues.
We also updated Jira Service Desk from 4.0.2 to 4.13.0
For those who stumble upon this, it's being corrected by the vendor here :
https://productsupport.adaptavist.com/browse/SRJIRA-4829
Related to Scriptrunner plugin
Hi @Mark Milford ,
Do you use any specific add-ons to fill these dropdown or perhaps behaviours?
if they don't load correctly you can always open a developer console on your browser (e.g. F12 on Chrome) and see if they throw any errors.
A screenshot is also helpfull so we can better analyze the problem!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, nothing crazy there. We are only running a 6 or so plugins in Jira (Scriptrunner, Automation, etc) but do nothing of the sort with the customer portal. We opened a ticket with Atlassian and included screenshots.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well i've had a similar issue with Scriptrunner on that version. I suggest disabling that for a moment and seeting if it helps.
Even on projects where there were no behaviours defined the check broke the loading of the screens.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting! Were you able to isolate to scriptrunner via disabling it / running in safe mode?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dirk - you were correct! Disabled Scriptrunner, and the drop down works again! Shoot, we are running the latest version (6.12.0). Investigating now....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
remember you cannot downgrade below 6.0.0 as it has breaking changes below that version.
I suggest the developer console and opening a ticket with them.. for me it showed something like:
Unhandled promise rejection TypeError object doesn't support property or method 'finally'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't see this as a reported issue on jira.atlassian.com.
Have you updated service desk after you moved to 8.13?
Are there any issues appearing in the application logs?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply!
We updated Jira Service desk from 4.0.2 to 4.13.0 at the same time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is definitely abnormal behaviour. Review the logs for any hints about what could be happening and engage atlassian's support team to see if they can help provide a resolution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Stephen - we opened a ticket and threw in some screenshots.
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.