This is essential for our users because all the information of our cases is being registered in a Salesforce Rich text area, so when it is pushed into JIRA it shows all the tags and it is quite difficult to understand for our support team when the description has a lot of information.
This has been a big item from our customers. They format out steps (Bold, Number, Bullets) in their documentation, but then it becomes a mess when it syncs. And they would like to use tables to help create stores and details to be clear. This has been a bit limitation on getting users to document well.
Kevin Lew
This is a pretty major issue for our users. Users waste time manually removing HTML tags in JIRA. Please prioritize.
Attachments Open full size
This is essential for our users because all the information of our cases is being registered in a Salesforce Rich text area, so when it is pushed into JIRA it shows all the tags and it is quite difficult to understand for our support team when the description has a lot of information.
Attachments Open full size
This has been a big item from our customers. They format out steps (Bold, Number, Bullets) in their documentation, but then it becomes a mess when it syncs. And they would like to use tables to help create stores and details to be clear. This has been a bit limitation on getting users to document well.
Attachments Open full size
It would be nice to have this resolved as otherwise the user will have to manually remove those html tags while creating the issue.
Attachments Open full size