It's all about the answers!

Ask a question

REST or OSLC Query for TeamArea/something


David Evans (1241730) | asked Sep 11, 11:13 a.m.

Greetings,


After hitting a wall with using the REST API to query for work items for a given team (I tried teamArea/itemId=, teamArea/name=, and teamArea/uniqueId=, but those are all non-queryable), I am beginning to think there is not a simple way to query for work items by Team Area using the REST API.

Is there a way to simply query for work items by name using either OSLC or REST? I am fine with either. Although, the OSLC API is complex enough that I typically use REST for my little tools and custom reports.

Thanks,
Dave

2 answers



permanent link
Sudipto Sarkar (63326) | answered Sep 11, 11:30 a.m.
Hey Dave,
If you want to search a workitem using its id, the simple query is:


You can get the uuid from the project catalogue.
The above query will give you list of project areas with its services.xml



permanent link
Jim Amsden (19336) | answered Sep 11, 11:47 a.m.

 For complex queries, you could use an RTC stored query or JRS report. 


To programmatically execute an RTC stored query and get XML, see Using Stored Queries.

To programmatically execute a JRS report, you dan use the data service URL available from the Export report to Microsoft Excel page (e.g., https://jazz.net/rs/query/22769/dataservice?report=22556&limit=-1&basicAuthenticationEnabled=true) or you can capture the query from the Format Results tab in Report Builder and execute it against the LQE SPARQL endpoint.

The problem with OSLC queries is that many of the fields you are looking for (e.g., team area) are URLs, not string names.


Comments
David Evans commented Sep 11, 3:44 p.m.

 This seems like it could be a good answer. Is there any way to filter what attributes I need returned? I am seeing a gigantic amount of attributes I do not need to access with this tool I am building, so the giant response is slow and inefficient.

Your answer


Register or to post your answer.