Replies: 3 comments
-
Hi @MattPD, This is how the input you mentioned is converted in my installation (v8.22.1). (which looks correct)
|
Beta Was this translation helpful? Give feedback.
-
Interesting, that does show |
Beta Was this translation helpful? Give feedback.
-
I'm hitting this issue, too, using the same "Markin" plugin. An option to skip the preprocessing would be great, I think. I've been supplying the "description" field from stdin rather than a template file, if that makes a difference. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, when creating an issue using
--template
, triple backticks ``` (in the template file used as input) surrounded by newlines are replaced with{code]
without newlines.For example, the original:
a
```
b
c
d
```
is replaced with
a{code}bcd
The problem is that the newline originally present after
a
is missing. The replacement of ``` with{code}
is also undesirable.The reason for these two issues being a problem for the particular Jira instance is that it already has a Markdown plugin, so this breaks the formatting for created Jiras (and the missing newline makes code portions unreadable).
Is there a way to pass the raw input in template file as-is, without any changes or replacements?
Edit: FWIW, I've also tried using
[code}
directly in the input template file, but that turned out to be even worse: The rewrites now introduce{code}
after several blank lines in the source code seemingly at random (?)--I wasn't able to determine the pattern thus far. For now I'm using triple backticks ``` and manually re-inserting the newlines in the web editor, hopefully there's a better way...Beta Was this translation helpful? Give feedback.
All reactions