Redmine › Extended Fields

So it’s not what I thought. After more investigation, I’ve determined that the email rendering path in redmine is unfriendly to html-safe values. What that means is while I can have html in a template for a field value which renders correctly in the issue view in a browser, the same value will not render correctly for email. This is because the email rendering path concatenates the field value with strings which aren’t html-safe. When you use string operations which merge safe and unsafe strings, the resulting string is unsafe.

That’s why the email gets the escaped html for the field value. (<a href ... instead of <a href ...). The problem is that the functions which handle the rendering of field values for email live in the redmine core, not in a plugin. I’d either have to submit a patch to redmine or find a way to override the offending functions in redmine.

The offending redmine code is here: https://gist.github.com/binaryphile/7873836. While my value is correctly returned as html-safe by `show_value(value)`, using interpolation on it in the `email_issue_attributes` method turns it unsafe: `#{value.custom_field.name}: show_value(value)”.

It looks like the `join("\n”)` in `render_email_issue_attributes` also makes it unsafe.

I’m trying to figure it out, thought I’d just post my progress in case anyone else comes across the same issue.

I ended up fixing it using my own plugin this way: https://github.com/binaryphile/redmine-2.3-plugins/commit/a597ccdd9791cfa5cbeb7b85e79ad4d912627433.