Jira API edit issue with null parent results in error "We couldn't save your changes. Copy your content, then try reloading the page."

When doing Edit issue PUT /rest/api/3/issue/{issueIdOrKey} by Jira API with body like:

{
    "fields": {
        "parent": null
    }
}

Then it behaves for team managed project:

  • OK, when the issue had some parent before (the parent is removed by the operation).
  • Fails with error 500 “We couldn’t save your changes. Copy your content, then try reloading the page.” when the issue has no parent.

So, such request never pass when issued 2 times. IMHO it breaks REST principles.

I have no such problem with description field, or custom fields: they may be set to null repeatedly. Also, company managed project seems working well, too.

1 Like