🚀 Added
- Added
ConvertFrom-AtlassianDocumentFormatpublic function (aliasConvertFrom-ADF) — converts ADF objects (Jira Cloud v3) to Markdown; plain strings (Data Center) are passed through unchanged. Supports headings, bold/italic/strikethrough/code/links, bullet/ordered/task lists, tables, code fences, blockquotes, panels, mentions, emoji, and date nodes - Added
ConvertTo-AtlassianDocumentFormatpublic function (aliasConvertTo-ADF) — converts Markdown to ADF for writing descriptions and comments on Jira Cloud v3. Supports all symmetric constructs: headings, inline marks, fenced code blocks, blockquotes, tables, task/bullet/ordered lists, block images - Added
Tests/Fixtures/adf.sample.json+Tests/Fixtures/adf.sample.md— reference fixtures covering every ADF node type, used by unit tests - Added nested list support (2 levels) for both
ConvertTo-ADFandConvertFrom-ADF— indented bullet/ordered lists are now parsed and rendered correctly - Added combined inline mark support (
***bold italic***,**_nested_**,_**reverse**_) — produces ADF text nodes with multiple marks - Added hard break support — trailing double-spaces in Markdown are converted to
hardBreakADF nodes and back
🔧 Fixed
- Fixed
ConvertTo-JiraCommentandConvertTo-JiraIssueto passBodyandDescriptionthroughConvertFrom-AtlassianDocumentFormat— Jira Cloud API v3 returns ADF objects instead of plain strings; without conversion, fields contained rawPSCustomObjectdata instead of readable text - Fixed table separator regex in
ConvertTo-ADFto handle compact separators without spaces (|---|---|) - Fixed
inlineCardrendering inConvertFrom-ADFto produce<url>instead of redundant[url](url) - Enforced UTF-8 with BOM across all PowerShell files for PS v5 compatibility (#574)