Create User Story is not working using OSLC 2.0 API
I have followed the given link but still not working , below error is coming :
https://rsjazz.wordpress.com/2022/02/02/ewm-work-item-oslc-cm-api/
Below are the details from Postman :
URL :- https://jazz.net/sandbox02-ccm/oslc/contexts/_BQSnUdPkEe-l4uedvx_w7A/workitems/defect
Headers :
Content-Type:application/json
Accept:application/json
OSLC-Core-Version:2.0
Request Body:-
{
"dcterms:title": "Your User Story Title",
"dcterms:description": "Description of the user story",
"rtc_cm:filedAgainst": {
"rdf:resource": "https://jazz.net/sandbox02-ccm/resource/itemOid/com.ibm.team.workitem.Category/_pGztYKfGEe-dn-YINNBc5Q",
"rdf:type": "http://jazz.net/xmlns/prod/jazz/rtc/cm/1.0/Category"
}
}
Error :-
Please provide help if anyone able to achieve this ........Thanks in Advance !
Error :-
{
"oslc:statusCode": 500,
"prefixes": {
"oslc": "http://open-services.net/ns/core#"
},
"oslc:message": "Save Status\nCRRTC0290E: The work item cannot be saved because the work item's type is not configured correctly at the project level. \nThe category is not from the same project area as the work item.\n",
"oslc:cause": {
"oslc:statusCode": 500,
"oslc:message": "Save Status"
}
}
Please provide help if anyone able to achieve this ........Thanks in Advance !
Comments
Ian Barnard
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 24, 9:39 a.m.The error message says: The work item cannot be saved because the work item's type is not configured correctly at the project level. \nThe category is not from the same project area as the work item.
Did you check this?
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 24, 5:16 p.m.This is the second question around the same stuff, ignoring the error message and the answers.
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 24, 5:10 p.m.I don't know, how often I have provided this link already. If you want to start with OSLC, maybe follow this post: https://rsjazz.wordpress.com/2022/02/02/ewm-work-item-oslc-cm-api/ and note that I did also something wrong using application/json. It might work, but the public API documentation does not list this as a valid header.