Please see details here:
The documentation and comunity users state that DEFAULT is FALSE, but this is not the case when migrating from CLOUD.
Please provide a step by step guide to get the documentation DEFAULT.
I want the jira.websudo.is.disabled = false
Best regards,
Sven Liang Jensen
0. select * from <jiradb.jiraschema>.propertyentry where property_key like '%websudo%';
Returns ID 10216 and proertytype 1 (true).
10216 jira.properties 1 jira.websudo.is.disabled 1
WORKAROUND IF 0. APPLIES
1. Stop Atlassian JIRA Service
2. Backup JIRA SQL database (full).
3. UPDATE <jiradb.jiraschema>.propertyentry set propertytype=0 where id=10216;
4. Start Atlassian JIRA Service.
5. Verify problem solved
Hi Sven,
Sorry to hear you have encountered this bug as reported in https://jira.atlassian.com/browse/JRASERVER-44554
However from reading the work-around in that bug ticket, and the KB https://confluence.atlassian.com/kb/websudo-is-disabled-after-migration-from-jira-cloud-to-jira-server-845939463.html
It does appear that both indicate to use the SQL select query to find that property in the table and then update it.
Can you confirm that making this change to the table in the database and restarting Jira has enabled this websudo feature again in your instance?
Please let us know.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.