Problem with filtring resources using field param via REST
I need to filter results using "title" field via REST API (https://jazz.net/wiki/bin/view/Main/RqmApi).
I use following URL:
https://SERVER_NAME:9444/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/PROJECT_NAME/testcase?fields=feed/entry/content/testcase/*
Of coures SERVER_NAME, PROJECT_NAME and TEST_CASE_TITLE are valid names.
The result contains all available TestCases. Filtring is not working in this case.
Should I do something in different way? Maybe my URL is incorrect?
I am using following version of software:
Quality Management - Core Libraries 3.0 Beta3
Jazz Foundation - Core Libraries 3.0.1 Beta 3
I use following URL:
https://SERVER_NAME:9444/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/PROJECT_NAME/testcase?fields=feed/entry/content/testcase/*
Of coures SERVER_NAME, PROJECT_NAME and TEST_CASE_TITLE are valid names.
The result contains all available TestCases. Filtring is not working in this case.
Should I do something in different way? Maybe my URL is incorrect?
I am using following version of software:
Quality Management - Core Libraries 3.0 Beta3
Jazz Foundation - Core Libraries 3.0.1 Beta 3
One answer
I need to filter results using "title" field via REST API (https://jazz.net/wiki/bin/view/Main/RqmApi).
I use following URL:
https://SERVER_NAME:9444/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/PROJECT_NAME/testcase?fields=feed/entry/content/testcase/*
Of coures SERVER_NAME, PROJECT_NAME and TEST_CASE_TITLE are valid names.
The result contains all available TestCases. Filtring is not working in this case.
Should I do something in different way? Maybe my URL is incorrect?
I am using following version of software:
Quality Management - Core Libraries 3.0 Beta3
Jazz Foundation - Core Libraries 3.0.1 Beta 3
The URL is correct (see https://jazz.net/wiki/bin/view/Main/RqmApi#FieldsExamples for more examples) using the RQM 3.0.1 GA candidate (I20110602_0806). If there was an issue with the RQM 3.0 Beta3 install, it has since been fixed.