Hi,
Currently we face an issue:
If a customer sends a requests which has a Wiki Markup rule, it changes the customer request.
Example:
"Hi, I have issues with my code:
<p>You wrote: {{ name }}</p>
Thanks"
It changes {{ name }} to name monospaced.
How can I counter this?
Thanks
Gualter,
I wouldn't recommend this, but to avoid that you would need to change the default text renderer:
Be aware this would change the renderer for that field in all circumstances, whether your user created the ticket by email or not. This is changing a basic functionality of Jira so you will need to let your team know you are disabling this.
Otherwise, they could use something like {noformat} surrounding the {{name}} usage that tells Jira not to format that particular part of the message.
Regards,
Shannon
Shannon,
Thank you for the reply. I will try this.
Since I use JIRA SD as an external user tool I cannot force my customers to to use a wrapper inside their code as they do not know of this limitation.
I need to be able to see the message contents without any special rendering.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gualter,
Once you give it a try, if you have any trouble, please let us know.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the worst it can happen if I change the rendering of the fields I want? Worst case my team looses the option to wiki render their text right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gualter,
That's correct, those existing fields would lose their ability to style text with wiki rendering.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.