nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Status Transition doesn't work via automation in JSON

Timur_2punyc

Hello dear community -

I did an automation in JSON to automate the Jira Status Transition:

{ "update": { "labels": [ { "add": "clone" } ], "issuelinks": [ { "add": { "type": { "name": "Cloners" }, "outwardIssue": { "key": "{{issue.key}}" } } } ] }, "fields": { "customfield_10032": { "value": "{{triggerIssue.customfield_10032.value}}" } }, "transition": { "id": "42" } }

The problem that this status transition doesnt work.

Any ideas why?

Thanks a lot in advance!

BR

Tim

Accepted answers

All comments

Trudy P Claspill

Hello @Timur

Welcome to the Atlassian community.

Is this in the context of an Automation Rule? If so, when asking for help with an Automation Rule it will enable us to help you more effectively if you provide:

1. Screen images that show your entire Automation Rule,

2. Screen images showing the details of the step(s) that are not yielding the results you expect,

3. Screen images that show the complete audit log output from the execution of the automation rule.

Can you provide a link to the source material that states you can transition an issue through the JSON code? I don't believe that is actual possible, but would be happy to be proven wrong by seeing reliable documentation that states it can be done.

Timur_2punyc

Hi @Trudy P Claspill -

Thanks a lot!

Here ist a screenshot:

Screenshot 2025-04-02 at 23.45.06.png

Here the corresponding code:

{
"update": {
"labels": [
{
"add": "clone"
}
],
"issuelinks": [
{
"add": {
"type": {
"name": "Cloners"
},
"outwardIssue": {
"key": "{{issue.key}}"
}
}
}
]
},
"fields": {
"customfield_10032": {
"value": "{{triggerIssue.customfield_10032.value}}"
}
},
"transition": {
"id": "42"
}
}

Screenshot 2025-04-02 at 23.48.02.png

Here the corresponding code:

{
"update": {
"comment": [
{
"add": {
"body": "Thanks for raising {{issue.key}}."
}
}
]
},
"fields": {
"resolution": {
"name": "Fixed"
}
}
}

In the audits is everything correct..

Looking forward to your answer!

Trudy P Claspill

Thank you for those screen images.

Can you provide a link to the source material that states you can transition an issue through the JSON code?

I don't believe that is actual possible, but would be happy to be proven wrong by seeing reliable documentation that states it can be done.

Timur_2punyc

"Can you provide a link to the source material that states you can transition an issue through the JSON code? "
We did not find any code, we just wrote it using your guides...

So you mean that it is not possible via automation to change the Transition an Issue + Category? We need it to create automatically new yearly events after we put them to DONE.

Bill Sheboy

Hi @Timur -- Welcome to the Atlassian Community!

Even though the Create Issue endpoint supports immediately transitioning, I recall my experimentation last year showed the automation rule actions for Create and Clone do not support this in the manner they use the endpoint. Instead they always fail with invalid JSON errors.

Instead, you can use the Send Web Request action to call the endpoint and supply your fields. For a short example, this JSON works:

{
  "fields": {
    "project": {
      "id": "12345"
    },
    "summary": "create issue in a different status using send web request",
    "issuetype": {
      "id": "10001"
    }
  },
  "transition" : {
    "id": "31"
  }
}

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud