Is your feature request related to a problem? Please describe.
Currently, the JIRA access token is stored within this plugin's directory (${vault.configDir}/obsidian-jira-issue/data.json), which means that using the core Obsidian Sync plugin with the "Installed community plugins" setting on results in this access token being synced. While this may be convenient, I would personally rather sync only the non-sensitive plugin settings and data and have access tokens stored only locally, even if that means I have to enter the access token on multiple devices.
Describe the solution you'd like
In my testing, files in the vault config dir, but outside of plugin dirs (for example: ${vault.configDir}/jira-auth.json), are not included when syncing the plugin lists and settings. If possible, I'd like the ability to opt-in to that location for the storage of my JIRA access token by this plugin.
Thanks for your time! I'd also be happy to attempt contributing this change if you're open to that.
Is your feature request related to a problem? Please describe. Currently, the JIRA access token is stored within this plugin's directory (
${vault.configDir}/obsidian-jira-issue/data.json), which means that using the core Obsidian Sync plugin with the "Installed community plugins" setting on results in this access token being synced. While this may be convenient, I would personally rather sync only the non-sensitive plugin settings and data and have access tokens stored only locally, even if that means I have to enter the access token on multiple devices.Describe the solution you'd like In my testing, files in the vault config dir, but outside of plugin dirs (for example:
${vault.configDir}/jira-auth.json), are not included when syncing the plugin lists and settings. If possible, I'd like the ability to opt-in to that location for the storage of my JIRA access token by this plugin.Thanks for your time! I'd also be happy to attempt contributing this change if you're open to that.