There are 2 updates, 1 comment.
 
 
Release Notes Application / cid:jira-generated-image-avatar-eee2cb73-a44e-4a75-aa16-91a63246a76c RN-115 Reopened

Add REST endpoints to create and list release notes and changes

 
View issue   ยท   Add comment
 

2 updates

 
cid:jira-generated-image-avatar-b9c8ef5b-cf12-4d62-bc17-28fddfd082cd Changes by Vincent Massol on 09/Sep/26 16:03
 
Resolution: Fixed
Status: Closed Reopened
 
 

1 comment

 
cid:jira-generated-image-avatar-b9c8ef5b-cf12-4d62-bc17-28fddfd082cd Vincent Massol on 09/Sep/26 16:03
 

Reopening rather than filing a new issue, since the REST endpoints this issue added are not released yet (2.7 is still in development) and the rule is to fix such a defect under the issue that introduced it.

The two endpoints that create something answer 201 Created with a body built from the request rather than from the page they just wrote, so a client is told values the wiki does not hold. Creation is template-driven, and a property the caller leaves out holds the value its template gives it, so every such default was reported as null:

  • POST .../changes without an importance answers "importance": null while the page it created stores the 1 (Medium) that ChangeTemplate gives it since RN-117.
  • POST /releasenotes without a product answers no product while the page it created holds the product configured for the wiki.

These endpoints exist to be called by an agent creating release notes, which is precisely a client that trusts the 201 body and records from it. Both are fixed together: the created page is read back and answered, instead of the request being echoed.