-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
None
-
1
-
Summary
Notifications are not rendering text formatting correctly and it's sending as a plain text with some pieces of the code
Steps to Reproduce
- Configure the "User Default Settings" (http://JIRA_URL/secure/admin/ViewUserDefaultSettings.jspa) to use HTML as the "Default outgoing email format"
- Edit a description field and add some colors and formatting to the text like the example below:
{color:#14892c}*Acceptance Criteria:*{color} 1. testing 123 ---- {color:#654982}*Development and Testing Artifacts:*{color}
Expected Results
According to our documentation (Configuring renderers - Implications for JIRA operations) when using the Atlassian wiki renderer, the rendered content (i.e. exactly what you see on the 'View Issue' page) will be sent out in the emails. This will create emails which are as rich as the content makes it.
If using the wiki style renderer, this is the preferred type of email since it is a real representation of the wiki markup.
Actual Results
We'll get the email notification without the text being formatted
Workaround
None
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-16352] Outgoing mail notification is not rendering the text correctly
I think this bug should be re-considered. This is a bug not a suggestion.
When the basic functionality you mentioned on the documentation page "[Configuring renderers|https://confluence.atlassian.com/adminjiracloud/configuring-renderers-776636458.html]" is broken, the decision should not depend on the demand.
Please reconsider your decision.
Thanks
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.
To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.
Regards,
Jira Server and Data Center Product Management
I agree to above point. This shouldn't be closed without a fix by stating "limited demand".