Hi,
according to https://confluence.atlassian.com/jiracorecloud/the-new-jira-issue-view-938040503.html
the new issue view renders markdown properly.
However, after importing github exports (Json to csv without any additional formatting), it looks like formatting is incorrect, as you can see, the code block is not rendered properly on the new issue view. Is this something that is still in progress?
Hello Zsolt,
Thank you for raising this question.
Have you checked if the markup works with the old view of JIRA?
The new issue view renders markdown properly, however, it must be specified in the file the parameter to render the Markup: {code:java} {code}
Can you please provide us how the markup is being addressed in the import file? I don't see any command that could be added to JIRA to use the code format.
Hi,
- the ticket itself comes from Github. We exported all issues of a repository from GH into JSON, converted it into JSON and imported it into JIRA software.
- the text is not rendering correctly in normal/old view either.
- as for the code formatting, that's part of the general markdown that github is supporting.
- the general question is, what's the best practice to import Github ticket into Jira whilst keeping all markdown formatting?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, one more question: "it must be specified in the file the parameter to render the Markup: {code:java} {code}" : in which file, sorry?
That looks like a markdown formatting we'd have to use after the issues have been imported? We're looking for a solution where we don't have to convert the Github export to anything else, given that supposedly the new views will support markdown.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bumping this thread as I haven't gotten an answer yet and we're still working on the GH->Jira issue export on our end. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Petter Gonçalves , sorry, but have to bump this again.
Seems like we're having the same issues with the task lists / checkbox lists as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Zsolt,
I think we will need to dig a little bit more into this to find the root cause of this behavior. Could you please open a support ticket with our standard Support? here's the link:
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.