How to fetch workflow with dc:identifier=2 using OSLC?
Jayesh S (11●3●6)
| asked Jan 30 '14, 1:10 a.m.
edited Jan 30 '14, 3:14 a.m. by Krzysztof Kaźmierczyk (7.5k●4●80●103)
Please frame a query for the below xml data to fetch dc:identifier=2
Accept Header is application/xml <oslc_cm:Collection xmlns:oslc_cm="http://open-services.net/xmlns/cm/1.0/" oslc_cm:totalCount="6" xmlns:dc="http://purl.org/dc/terms/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rtc_cm="http://jazz.net/xmlns/prod/jazz/rtc/cm/1.0/"><rtc_cm:Status rdf:resource="https://jazz.visteon.com:9443/ccm/oslc/workflows/_r_o5UJthEeGYYPMfxStaiQ/states/com.ibm.team.workitem.defectWorkflow/2"> <dc:identifier>2</dc:identifier> <dc:title>In Progress</dc:title> <rtc_cm:iconUrl>https://jazz.visteon.com:9443/ccm/service/com.ibm.team.workitem.common.internal.model.IImageContentService/processattachment/_r_o5UJthEeGYYPMfxStaiQ/workflow/inprogress.gif</rtc_cm:iconUrl> <rtc_cm:group>inprogress</rtc_cm:group> </rtc_cm:Status> <rtc_cm:Status rdf:resource="https://jazz.visteon.com:9443/ccm/oslc/workflows/_r_o5UJthEeGYYPMfxStaiQ/states/com.ibm.team.workitem.defectWorkflow/1"> <dc:identifier>1</dc:identifier> <dc:title>New</dc:title> <rtc_cm:iconUrl>https://jazz.visteon.com:9443/ccm/service/com.ibm.team.workitem.common.internal.model.IImageContentService/processattachment/_r_o5UJthEeGYYPMfxStaiQ/workflow/open.gif</rtc_cm:iconUrl> <rtc_cm:group>open</rtc_cm:group> </rtc_cm:Status> <rtc_cm:Status rdf:resource="https://jazz.visteon.com:9443/ccm/oslc/workflows/_r_o5UJthEeGYYPMfxStaiQ/states/com.ibm.team.workitem.defectWorkflow/6"> <dc:identifier>6</dc:identifier> <dc:title>Reopened</dc:title> <rtc_cm:iconUrl>https://jazz.visteon.com:9443/ccm/service/com.ibm.team.workitem.common.internal.model.IImageContentService/processattachment/_r_o5UJthEeGYYPMfxStaiQ/workflow/reopen.gif</rtc_cm:iconUrl> <rtc_cm:group>open</rtc_cm:group> </rtc_cm:Status> <rtc_cm:Status rdf:resource="https://jazz.visteon.com:9443/ccm/oslc/workflows/_r_o5UJthEeGYYPMfxStaiQ/states/com.ibm.team.workitem.defectWorkflow/3"> <dc:identifier>3</dc:identifier> <dc:title>Resolved</dc:title> <rtc_cm:iconUrl>https://jazz.visteon.com:9443/ccm/service/com.ibm.team.workitem.common.internal.model.IImageContentService/processattachment/_r_o5UJthEeGYYPMfxStaiQ/workflow/resolve.gif</rtc_cm:iconUrl> <rtc_cm:group>closed</rtc_cm:group> </rtc_cm:Status> <rtc_cm:Status rdf:resource="https://jazz.visteon.com:9443/ccm/oslc/workflows/_r_o5UJthEeGYYPMfxStaiQ/states/com.ibm.team.workitem.defectWorkflow/4"> <dc:identifier>4</dc:identifier> <dc:title>Closed</dc:title> <rtc_cm:iconUrl>https://jazz.visteon.com:9443/ccm/service/com.ibm.team.workitem.common.internal.model.IImageContentService/processattachment/_r_o5UJthEeGYYPMfxStaiQ/workflow/close.gif</rtc_cm:iconUrl> <rtc_cm:group>closed</rtc_cm:group> </rtc_cm:Status> <rtc_cm:Status rdf:resource="https://jazz.visteon.com:9443/ccm/oslc/workflows/_r_o5UJthEeGYYPMfxStaiQ/states/com.ibm.team.workitem.defectWorkflow/com.ibm.team.workitem.defectWorkflow.state.s7"> <dc:identifier>com.ibm.team.workitem.defectWorkflow.state.s7</dc:identifier> <dc:title>Deferred</dc:title> <rtc_cm:iconUrl>https://jazz.visteon.com:9443/ccm/service/com.ibm.team.workitem.common.internal.model.IImageContentService/processattachment/_r_o5UJthEeGYYPMfxStaiQ/workflow/defer.gif</rtc_cm:iconUrl> <rtc_cm:group>open</rtc_cm:group> </rtc_cm:Status> </oslc_cm:Collection> Thanks Jayesh.S |
3 answers
Hello,
right - expected.
Please refer to https://jazz.net/wiki/bin/view/Main/WorkItemAPIsForOSLCCM20#Getting_Representations
You may use
https://jazz.server.com:9443/ccm/resource/itemName/com.ibm.team.workitem.WorkItem/2
Eric
|
Hello,
not sure I understand the question, and what information you want to fetch.
May you please add more details?
Thanks,
Eric
|
I want to fetch workitem data with dc:identifier=2 by using query syntax where
https://jazz.server.com:9443/ccm/oslc/contexts/_r_o5UJthEeGYYPMfxStaiQ/workitems?oslc_cm.where=dc:identifier="2" but it is not working |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.