If you are going to post about something that you have decided is possibly a bug why not post it as a GitHub issue? The support template on this forum does state, "If this is a bug report, please create it on GitHub instead.
I only mention this as I try to keep an eye on posts to the Support section for those who need help to install / use / configure Joplin. At the moment I log in to find multiple posts marked "BUG ?" drowning out the support posts and most if not all of these are more minor issues with the Rich-Text Editor. I also notice that these posts are now being transferred to GitHub anyway.
Do you think it may be better to post these as issues on GitHub where the devs can keep track of them and assess them, or is it just me?
Sorry man if you have lost your time because of me.
My workflow is simple :
BUG ? - (no reason to bother devs for maybe nothing ; light of community is needed and it's the beauty of a forum : everyone learns from everyone)
BUG => GITHUB - (I will be happy if devs can solve the issue that stops the fluidity of my own work; I'm not a "customer" I'm an user...)
FIXED - (I'm happy the issue is solved ; it's important to inform the others who try to help in order to not loose time with something solved).
This workflow is in the title of my topics (!) so you and other devs can have a look at my topics when you have time and not immediatly (when you see "BUG ?")… At the right moment it goes on GITHUB (BUG => GITHUB).
OK, I was just suggesting that rather than create your own private custom workflow within the Joplin support forum, you could use GitHub issues for possible bugs, just like the devs asked.
I do that. And during the first phase, I start my topics with "Before reporting this maybe bug to GITHUB"... Sorry again if you have loose time because of me. Now, you know my way of working.
