Open Bloodsucker opened 1 year ago
With the current implementation you can create a tag for a specific account using the full URL. https://marc0l92.github.io/obsidian-jira-issue/docs/configuration/rendering#issue-url-to-tag
If you use the JIRA:
prefix the plugin will check all your account starting with the one with more priority.
You can try with those approaches while I work on the features you proposed.
Thank you for considering my suggestion. I didn't know about your feature, so thanks!
Is your feature request related to a problem? Please describe.
The plugin uses the so-called Inline Issue Prefix (default:
JIRA:
) to detect jira issues and do the magic. However, multiple jira accounts might be configured which will surely cause issues. The configuration as it is right now is a problem if an account is removed or stops being accessible.Describe the solution you'd like
Allow the Inline Issue Prefix to be configured per account, instead than of globally.
Describe alternatives you've considered
--
Additional context
Additionally, I strongly suggest to add some sort of ignore flag per account so that when set the engine will ignore fetching to the API. This can be very useful if certain credentials stop being accessible, otherwise the notes will start appearing with a bunch of 404 error links.