You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have attached a sequence of screenshots showing:
The source markdown that includes mixed ordered and unordered nested lists (also see below).
The current markdown2confluence output; neither indenting or ordered/unordered lists are correctly converted.
What the output looks like when put into Jira.
What the Jira markup should look like to capture the nested lists (both ordered and unordered).
How Jira displays the correct markup.
Here is a snipit of my markdown that is used in the screenshots:
* Will need to add myself to project, may need to add to group in project for authorizations and/or workflow
1. Server Manager > Administer Users and Groups > Users
1. Action Menu > Edit Project Assignment
1. Find Project/Site in list.
1. Click on left-most check box, Ad Roles radio button, both right-most checkboxes.
* Customers should have some content in the CMS (it doesn't have to be much).
1. They must chose where the test and production sites will publish.
* Our hosting server (bold.doit.wisc.edu) - used for test, DoIT Shared Hosting,
* Their departmental hosting - If any other place than our hosting server or DoIT SharedHosting we need SFTP usernames and passwords for their test and production sites.
* Usually the DNS name for the test site will start with "wwwtest." e.g., wwwtest.quality.wisc.edu
* Normal DNS for production, e.g., quality.wisc.edu or www.quality.wisc.edu
* We configure both prod/test sites at the same time.
* Obfuscate prod username by adding '-DISABLED' to the uid to prevent publishing. When prod is ready, simply remove '-DISABLED' to publish site to production hosts.
* Do the configuration workflow "CMS Publication Configuration" on the CampusCMS wiki [https://wiki.doit.wisc.edu/confluence/display/CMS/CMS+Publication+Configuration](https://wiki.doit.wisc.edu/confluence/display/CMS/CMS+Publication+Configuration)
It's interesting that markdown uses indenting to determine nesting while Jira uses multiple symbols:
The markdown is much easier to read, which, of course, is the point. The current markdown2confluence preserves indenting but does not do the correct markup. I did a test and the Jira markup still works indented! So it looks like the only change (!) is to track the indenting and put the right number of * or # and they can remain in the first column. This produces correct results: