No, Jira does not let you read (“per se“) the markup source of an “issue” – that’s why I went this way in the first place 🙄
- http://Jochen.Hayek.name/wp/blog-en/2015/12/02/jira-rest-api/ – using Jira’s REST API: a “…/rest/api/2/issue/…” URL
- http://Jochen.Hayek.name/wp/blog-en/2015/12/22/jq-json-processor/ – how to use
jq
for json-tidying
jq . X.json > X.pretty.json
- http://Jochen.Hayek.name/wp/blog-en/2018/01/17/json-extract-structure/ – extract the structure tree of your JSON data using
jq
and a nice command line
jq -c 'path(..)|[.[]|tostring]|join("/")|"."+.' X.pretty.json
- the field we are interested in is
fields/description
jq ".fields.description" X.json > X.description.txt
- save the value of that field to a separate file!
- remove the leading and trailing double-quotes!
- replace all
\"
with ordinary double-quotes! - remove
\r
! - replace
\n
with ordinary new-lines!
jq ".fields.description" X.json | perl -pe 's/^"(.*)"$/$1/; s/\\"/"/g; s/\\r//g; s/\\n/\n/g' > X.description.txt
- …
- looks good, doesn’t it?