hey, you might try updating the admin_accounts directly as a work around, but if that doesnt take effect, check any related config files or logs for clues. make sure you backup the data befor u update anything
I encountered a similar situation with an older version of JIRA where the usual membership tables were absent. What ultimately worked for me was ensuring that the update correctly targeted the specific admin account records. I first verified through the logs that the database changes were being picked up by JIRA. Another key step was restarting the application after making the database updates, which allowed the changes to take effect. It’s crucial to backup the database before making any modifications and to check if there are any additional configuration files that need updating.
The approach I took was to address the situation by making sure every change was audited. I observed that even with the missing usual membership tables, it was necessary to work within the existing schema. Personally, I made changes directly to the admin records while ensuring that I captured a full backup of the database beforehand, reducing risk. After modifying the settings, I restarted the JIRA service so that all new configurations were properly read and applied. Checking server logs post-restart also helped confirm that the changes took effect as intended.
hey, try updating the admin record and then restart jira. i had a similar issue where a quick restart helped apply the changes. also, keep an eye on the logs if the update doesn’t reflect immediatly.