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; } } }

PUT rest/api/2/issue/ 500 error. Jira Rest API Error

Tronikel

Hello,

I’ve encountered a problem when calling PUT /rest/api/2/issue.
Jira Cloud responds with 500 and

{
  "errorMessages": [
    "We couldn't save your changes. Copy your content, then try reloading the page."
  ],
  "errors": {}
}

The field that I want to edit is an ace app Issue Field with type “rich_text”

More context to this error:

So, I am building an ace app, which has a connect module → Issue Field:

This field gets assigned/updated to a Jira Issue through my app, the request is shown below.

Now is the interesting part:

When I call the PUT request for the first time (on an issue which does not have my field assigned) it updates correctly.

But when I change the value and call PUT a second time (the issue already had my field assigned) the error pops up.

And, also, when I call PUT with the same value as the first PUT, it works.

e.g.

I create an Issue
Call PUT, value get saved correctly
Add a random letter to my current value at the end and call PUT, get error
Remove my random letter at the end and call PUT, then it works

So my guess is that my field is like a read-only field which you can only set once

BUT, everything works if I change my Issue Field type from “rich_text” to “text”. Sadly, I can’t do that because the 255 character limit is too small for my needs because I’m storing stringified JSON in it.

Thanks in advance for your time & help!

Accepted answers

Tronikel

Okay, so after like 3 days, without me doing anything, the problem disappeared, and I can edit the fields, strange.

But hey, it works now!

All comments

Tom Lister_fo1j4e

Hi @Tronikel

I am server based so I'm not sure if this applies to cloud in the same way...

Check if your field is on the edit page as this is checked by anything updating an issue.

"The fields that can be updated, in either the fields parameter or the update parameter, can be determined using the /rest/api/2/issue/{issueIdOrKey}/editmeta resource.
If a field is not configured to appear on the edit screen, then it will not be in the editmeta, and a field validation error will occur if it is submitted."

I'm wondering whether when a field has the same value as current Jira does not update so the call when the character is removed appears to work.

Tronikel

Hi @Tom Lister

This is what I'm getting when calling /rest/api/2/issue/{issueIdOrKey}/editmeta:

So, does this mean that I should be able to edit the issue field?

The full response is here, if it'll help: https://hastebin.com/agoluqozos.json

Thanks

Tom Lister_fo1j4e

Hi @Tronikel

Yes - if a field is in the edit metadata is should be updatable.

A 500 error code is usually a serious internal error in processing a request. Are you able to ask Atlassian to look at the logs for you and get more details. I think only site-admins, technical, or billing contacts on paid Cloud sites will have the ability to create such support requests.