It used to be possible to set the Description field in an Automation via the "more options" using JSON and ADF, see Solved: Updating description field using REST API and Atla... for reference.
I just tried it out again and am now getting an Error message stating
(Operation value must be a string (description))
Pretty sure the solution provided in the other thread worked at some point as I used that before.
My workaround now is to recreate the formatting via Markdown using the "normal" set Field option (no JSON). But my colleague needs a numbered header column which I cannot set via Markdown.
Any idea why ADF isn't working within the JSON anymore?
I tried updating description using below and it worked fine. Can you share what are your rule in Additional fields
{
"fields": {
"description": "Updating description using automation {{issue.key}}."
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.