Hi,
With the new issue view being rolled out in cloud instances and the new text editor coming with it, I am in the process of switching over from using the wiki-markup to the markdown syntax.
Problem description:
I am currently blocked by the Jira email-handler we use extensively in my organisation.
The Jira email handler is able to receive text formatted with the wiki markup, however, it seems that it is unable to process the markdown syntax.
For example, if I send this to an email handler (markdown syntax):
# Heading level 1
## Heading level 2
### Heading level 3
#### Heading level 4
##### Heading level 5
###### Heading level 6
Heading level 1
===============
Heading level 2
---------------
I just love **bold text**.
1. First item
8. Second item
3. Third item
5. Fourth item
when opening the task, the result is as follows:
It seems that when handling the email, Jira used the wiki-markup syntax to format the description instead of markdown.
If I try to edit the description using the new issue view, The following message displays:
Upon saving, the wiki-markup formatted text breaks, but is not replaced by the markdown syntax:
Only after removing and adding again the space between "#" and "Heading level 1" does the markdown syntax kick in:
Expected behaviour:
As Atlassian seems to be phasing out the wiki markup support for jira cloud, I would expect the mail handlers to follow the change and be able to handle the markdown syntax.
The new text editor should also be able to recognize markdown syntax coming from email handlers, without having to edit manually each line.
At the moment, this is a major blocker for our adoption of the new issue view. We rely heavily on email handlers to simplify our workflows.
I couldn't find any open topic or issue opened regarding this, maybe I missed it?
Many thanks,
Armand.