Get "Planned for"'s (iteration) itemid be used OSLC query key "iterationLabel"
![]()
日本語:
目的は ワークアイテムを検索するときに反復名をキーにして行うこと。 HTTP Get https://Jazzserver/ccm/oslc/contexts/_zyGbEA1IEeSp-s2XHor-aA/workitems?oslc.where=rtc_cm:plannedFor="https://Jazzserver/ccm/oslc/iterations/_MCrpwLnrEeWLIOToef9h7g"&oslc.select=dcterms:type,dcterms:identifier,dcterms:title,&oslc.orderBy=+dcterms:identifier 反復名(label)から下記IDを探すことができません。 "https://Jazzserver/ccm/oslc/iterations/_MCrpwLnrEeWLIOToef9h7g" いい手段はないでしょうか? In English Purpose to key "iteration name" when query "workitems" HTTP Get https://Jazzserver/ccm/oslc/contexts/_zyGbEA1IEeSp-s2XHor-aA/workitems?oslc.where=rtc_cm:plannedFor="https://Jazzserver/ccm/oslc/iterations/_MCrpwLnrEeWLIOToef9h7g"&oslc.select=dcterms:type,dcterms:identifier,dcterms:title,&oslc.orderBy=+dcterms:identifier I can not find the following ID from iteration name (label). "https://Jazzserver/ccm/oslc/iterations/_MCrpwLnrEeWLIOToef9h7g" I think a good way? |
Accepted answer
![]()
I assume you know how to get the project service provider URL since you have gone this far.
1. Access the project area service provider URL, such as https://clm:9443/ccm/oslc/contexts/_tNGM8IPsEeSNXIoymcU8qg/workitems/services.xml 2. In the response content, look for the "resourceShape" of the work item type that you're interested, for example: < oslc:resourceShape rdf:resource="https://clm:9443/ccm/oslc/context/_tNGM8IPsEeSNXIoymcU8qg/shapes/workitems/defect" / > 3. Access the resource shape URL as shown above. 4. In the response content, simply search "iterations", and you should find something like this: < rdf:Description rdf:about="https://clm:9443/ccm/oslc/context/_tNGM8IPsEeSNXIoymcU8qg/shapes/workitems/defect/property/target/allowedValues"> < rdf:type rdf:resource="http://open-services.net/ns/core#AllowedValues" / > < oslc:allowedValue rdf:resource="https://clm:9443/ccm/oslc/iterations/_tWgnoIPsEeSNXIoymcU8qg" / > < oslc:allowedValue rdf:resource="https://clm:9443/ccm/oslc/iterations/_tWgAk4PsEeSNXIoymcU8qg" / > < oslc:allowedValue rdf:resource="https://clm:9443/ccm/oslc/iterations/_tWgAkoPsEeSNXIoymcU8qg" / > < oslc:allowedValue rdf:resource="https://clm:9443/ccm/oslc/iterations/_tWgnoYPsEeSNXIoymcU8qg" / > < oslc:allowedValue rdf:resource="https://clm:9443/ccm/oslc/iterations/_tWgAkYPsEeSNXIoymcU8qg" / > < /rdf:Description> HIROAKI JOSAKO selected this answer as the correct answer
|
2 other answers
![]()
Indeed, is not the OSLC.
Versatility is not enough. However, that number of steps to information acquisition increases is not willing. While the RTC of the API specification does not change, we will use the InternalAPI. Thanks |