At the lowest level, this is correct, but I would not recommend accessing the property entry directly if the intent is to do this from code.
To find them in the database where they happen to live today:
SELECT pe.property_key, ps.propertyvalue FROM propertyentry pe INNER JOIN propertystring ps ON pe.id = ps.id WHERE entity_name = 'jira.properties' AND property_key LIKE 'com.atlassian.jira.lookandfeel:%';
If you want to do this from code, you should step out two layers, skipping over SAL's
PluginSettings to land at LookAndFeelProperties, the outward facing API that is actually provided for external access to them.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events