If you do that, I'm afraid you will get two "Resolved" activity logs. One with "This is an update" in the description, then the automatically generated activity log with "Status changed from 'XXXX' to 'Resolved'" in the description.
If you absolutely need to post a resolution comment, and if you want to avoid having a duplicate activity log, you need to add "status_f":"1" to the PUT call to cr. That LOCAL attribute is designed to inhibit the "Update Status" activity log creation.
The body of the POST to cr would be:
{
"cr":{
"status":{
"@REL_ATTR":"RE"
},
"status_f":"1"
}
}
I hope this helps
-------------------------------------------
Original Message:
Sent: Mar 17, 2026 10:06 AM
From: Sebastian Nagy
Subject: How to update status to 'Resolved' and insert comment same time via REST API
Hi Filipe,
I think there might a misunderstanding, in REST you are not able to create an object from another object, It seems REST does not enforce the must_comment flag, it's the REST client's responsibility to ensure the app follows the restrictions.
I was able to achieve the same outcome by making these calls:


I hope this helps.