Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
P5
-
Resolution: Won't Do
-
Affects Version/s: None
-
Fix Version/s: None
-
Template:customfield_11100 14053
-
Development Team:Spitfire
-
Epic Link:
Description
In detail, the request is:
PUT /notes/457498fb-3b3e-42c5-b23b-184ed2d67be4 { "text" : "This is the big guy.", "id" : "457498fb-3b3e-42c5-b23b-184ed2d67be4", "link" : "users/1ad737b0-d847-11e6-bf26-cec0c932ce01" }
And the response is:
422 Unprocessable Entity { "errors" : [ { "code" : "-1", "message" : "creatorUserName is required", "type" : "1", "parameters" : [ { "key" : "creatorUserName" } ] } ] }
So it looks like this is an instance of the known problem where the server-side modules (or possibly RMB, which underlies them) get confused about metadata fields.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
MODNOTES-31 "readonly" fields like creatorUserName, etc should be ignorable
-
- Closed
-
- relates to
-
RMB-92 PUT breaks when using metadata schema
-
- Closed
-
-
STSMACOM-55 Can't Edit Notes
-
- Closed
-
-
UIU-294 Get notes working under <SearchAndSort>
-
- Closed
-