We have created templates for users to be able to create issues from template.
In the created templates, we have applied styles to the content. For example, the template content looks like below:
But when we try to create an actual issue from template in one of the projects, the same content in the above template is displayed with markups like below.
This is getting complex if we have lengthy sentences in the template when we include examples, instructions etc., in the template. We are worried that this would be negative experience for our internal users and they may end up not using it.
Is there a way we could fix this and make the description in the "create issue" look exactly like the created template?
Hi @Balakrishnan and welcome to the community!
Also, if you have a repetitive business process, you can automate creation issues from templates using Business Process Manager (created by my SaaSJet team)
It allows creating issues templates with different fields: dropdowns, multi-choices, checkboxes, radio buttons, etc.
Hope, it will be useful for you
Regards
Hello @Balakrishnan,
Welcome to Atlassian Community!
On the create issue screen, the editor of the Description is Wiki Markup and it’s expected to show as plain text. It will only show the formatted text when clicking on “Preview”:
The editor on the Create issue screen was always like that on Jira Cloud, the only way to view the formatted text is by using the preview.
The view/edit screens in Jira changed with the new issue view and the editor is now Markdown (WYSIWYG), only the create screen wasn’t affected by this change, but it will be soon.
Please, check the latest update on the feature request ticket below:
Also, check this article that has more information:
With this said, there is nothing much to do now since the editor for the Description on the create screen will change to Markdown.
If you have any other questions regarding this matter, please let us know.
Kind regards,
Angélica
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.