Closed pmeinhardt closed 2 years ago
There's already a good improvement on the output.
Some weirdness I saw when trying it on tickets though:
 
in different places (which is just a "space" as far as I can tell):
on a URL from an inlineCard
ADF node:https\://bitcrowd.atlassian.net/browse
hardBreak
nodetext
nodes, e.g. 2\. double check…
media
elements which currently output <!-- media: file 80f76786-… -->
. I wonder whether we can derive their URL somehowStatus update: This is currently being tested internally at bitcrowd. 🧪
Testing 🥼
<https://...>
but work great (did not know this) ✅ (Just collecting some of my findings with the internal build here)
Quick rebase 🏓
Just to confirm: played around a bit with the auto-formatting of the description and it - of course - works like charm 💯
(It also shouldn't really be affected by this change right here)
Will do another round of test driving and then probably merge 🚢
This needs a bit more testing. We should try a development build with Jira tickets we have in the wild.
The Jira API is queried in a different way. We should possibly check what this means in terms of compatibility, esp. with regard to on-premise Jira installations (which could be older?).
Closes #291.