Problem Statement:
Jira Cloud's automatic issue-key linkification (Smart Links) incorrectly identifies issue keys within contiguous strings that represent Unix-style filesystem paths (e.g., symphony/SYMP/FEATURES/SYMP-6168/simple/t25).

Because the forward slash (/) is treated as a non-word character (\W) by the regex parser, it satisfies the word boundary (\b) requirement for issue-key detection (e.g., \b[A-Z]-\d\b). This causes the Jira Cloud ADF generator to split the literal path and insert an inlineCard node for the issue key segment.

Observed Behavior:

• Input (Plain Text): symphony/SYMP/FEATURES/SYMP-6168/simple/t25

• Actual Result (ADF): The segment SYMP-6168 is converted into a Smart Link (inline card), which renders the issue summary and status, breaking the visual and semantic continuity of the path.

• Persistence: Clearing the description_adf column does not resolve the issue, as the Jira Cloud renderer re-processes the plain-text description column and recreates the inlineCard immediately.

Impact:

• Corrupts filesystem paths, git branch references, and CLI commands in issue descriptions and comments.

• Affects data migrated from Jira Data Center where paths were stored as plain text.

• Requires manual or script-based remediation (wrapping in {}{{monospace{}}}) to "protect" the text from the auto-linker.

Suggested Fix:
Update the Jira Cloud auto-linkification regex/logic to ignore issue-key patterns when they are immediately adjacent to path separators (/) or other non-whitespace characters that indicate a contiguous literal string.

Workaround:
Wrap the affected path in monospaced formatting (e.g., {{path/to/PROJ-123}} in Wiki Markup or a code mark in ADF).