Closed KolyaKorruptis closed 3 years ago
Thanks for reporting this issue. Can you give me an example to reproduce the issue?
No, the doubling of issues happened too often and your response comes way too late. I stopped using the plugin because of this problem.
Did you replaced this plugin something else?
Well, I switched to Edge browser, which copy & pastes URLs with the title of the website as link text, into Joplin's rich text editor. In my job I create a lot of Jira issue links in Joplin and this helps a lot. While it can't tell me the status of an issue of course, it's a lot faster than fiddling with issue templates.
Thanks for your usage feedbacks. I'm deprecating the template I was using before in order to implement something more user friendly. In this markdown fence block you will be able to paste the user story link and then see the status in the rendered version.
I will close this issue when I release this new version
Will there be a button in the rich editor to mark text as jira issue? This would be preferable. Or will I have to create a code block, then specify the language as "jira-issue" and then paste the ticket number?
I don't know how the rich editor works from the plugin development point of view. I will take a look at it.
Do you know any existing plugin that allows some interactions in the rich editor? In this way I can take a look at their implementation
I seem to remember using a few plugins that had buttons in rich editor, but I don't know anymore which did. Sorry. Maybe I'll find the time to look them up later.
I will take a look at it as well, but from what I know:
I published a new major version where I redesign the full plugin. I hope that now this issue is fixed
I changed the options to include Render: assignee and hit Refresh issues. Afterwards every issue was inserted a second time in the mark down. First without the assignee and then again with the assignee.