What is the challenge? |
Markdown editing has been added in Azure DevOps for rich text fields. However, when the data is migrated to Aha, it's stored as raw Markdown rather than displaying as formatted text. |
What is the impact? |
Makes integrating data between the two systems challenging |
Describe your idea |
Improve integration by detecting Markdown text and rendering it in a formatted fashion within Aha |
This actually goes both ways, also when sending to DevOps, we should have the option to default to markdown if the engineers prefer that format for further editing of the work item, so:
Can we display the markdown correctly (i.e. formatted) when a record gets imported from DevOps, and
Can the integration send Aha! records to DevOps using Markdown, so engineers can use it as a default?