Describe the bug

Editing an issue does not convert markdown to jira markdown.

Please provide following details

1. JiraCLI Version:

   (Version="1.7.0", GitCommit="79067e2422df10e59f310bd6fd4979f43a1df0e7", CommitDate="2025-08-30T08:30:25+00:00", GoVersion="go1.24.1", Compiler="gc", Platform="darwin/arm64")

2. Are you using Jira cloud or on-premise jira server?on-prem

   SERVER INFO-----------Version:  10.3.15Build Number:  10030015Deployment Type: ServerDefault Locale:

3. What operating system are you using? Also mention version.

   macOS Sequoia 15.7.2

4. What terminal are you using? Also mention version.

   iTerm and vscode integrated terminal

To Reproduce

Steps to reproduce the behavior:

1. create an issue with a markdown bodyjira issue create -s 'test' -b'## heading'
2. view the issue in jira, the## heading markdown has been correctly converted to jira wiki syntax:h2. heading
3. edit the issuejira issue edit $KEY -b'## heading'

Expected behavior

The body was converted from markdown to jira wiki syntax, just likejira issue create

Actual behavior

The markdown gets submitted as-is, and jira interprests## heading as an ordered list.

Additional context

The decision to convert to jira MD is made here:

, based on a type assertion and theisADF flag. I think that's Atlassian Data Format, and my crusty on-prem jira server is probably not using it. I'm not sure what would be a more reliable heuristic to detect if MD conversion is needed, but a--use-jira-md CLI flag to force the conversion would work.