I opened a couple of Github issues about 6 weeks ago, Emails with inline css show all css · Issue #3011 · frappe/frappe · GitHub and Email parseaddr does not work as expected · Issue #3004 · frappe/frappe · GitHub . One concerns css markup showing inline in the email view which is about 40 lines long so looks very poor to users and other MS markup appearing everywhere but is easy enough to fix it would appear. Likewise I created a bug concerning email parsing with the new Email Inbox where emails with a name with the email that has a comma in it, breaks the parsing and can’t be automatically linked to an existing email address in ERPNext. ie
Robbins, Julian julian.robbins@abc.com would break this. This way of writing your name is very popular on emails in Europe.
Helpfully, two members of the community proposed pull requests very quickly after this, but there are issues with how the code is written, requirements of test cases and proof that the fixes actually the fix the code properly. I’m not a developer so cannot help with this myself.
But unfortunately both times these well written bug reports have been closed without any further input; I can appreciate and understand why but I’m not able to re-open the bug reports so they just get lost and appear to be either fixed or not real bugs when they very much are.
So two things:-
- How can I reopen the bugs ?
- How can the community try to handle these type of cases better ?
Julian