Convert Markdown to JIRA Markup and back during import/export
Descriptions of issues imported from JIRA should appear correctly. The same goes for export, when you export to JIRA, descriptions should appear correctly there.
Vladislavs Zaluckis
shared this idea
-
Cris S
commented
The value of JIRA integration (one of the key features of the product) is compromised by the lack of compatible markup or rendering support. This is my number one feature request for SoB.
-
Florian Hehlen
commented
fyi... Atlassian just announced that cloud jira will start supporting markdown in the comming weeks. I got this in an newsletter they sent me.
-
Krzysztof Jelski
commented
Bumped into this issue today. There's difference in 2nd level of indentation in list as already mentioned. Also bold in JIRA is with one * and in SOB with two **. The result is that you either have to not do any formatting or format in just one of the tools and ignore how it looks in the second one.
-
Alan J
commented
Please support the JIRA version of Markdown in SoB (i.e., the markdown implemented in 'wiki renderer' in JIRA). Then all will be in fine in both SoB and JIRA.
-
Daniel B
commented
personally having issue with indented bullet points where Jira requires **. This is not recognised/supported by SoB. thank you
-
Marc MINTEN (EVS)
commented
We are using JEditor, so synchronizing descriptions is not working as the description in SOB shows all the html tags, making the description unreadable.
Also pictures in the description field are not sychronized to SOB, we have a lot of pictures in Description fields... -
Pete
commented
An easier way might be to allow users to choose to use the JIRA version of Markdown instead of the version that you currently support. This would avoid having to convert the Markdown and the issues that could create.