In our subscription, we have a custom field called c_ThemeDeliveryOwner which is a single select User dropdown. It is intended to be used at the Theme level (the 3rd level up in the Portfolio Item hierarchy).
When using the field in a filter while querying at the Theme level, the WSAPI returns data as expected. Example:
https://rally1.rallydev.com/slm/webservice/v2.0/portfolioitem/theme?query=(c_ThemeDeliveryOwner%20=%20%22/user/<USER_OID>%22)
Returns:
{"QueryResult": {"_rallyAPIMajor": "2", "_rallyAPIMinor": "0", "Errors": [], "Warnings": [], "TotalResultCount": 2, "StartIndex": 1, "PageSize": 20, "Results": …..}
However, when querying lower level portfolio items (Features or Iterations), using this field with a Parent prefix throws an error. Example:
https://rally1.rallydev.com/slm/webservice/v2.0/portfolioitem/Iteration?query=(Parent.c_ThemeDeliveryOwner%20=%20%22/user/<USER_OID>%22)
Returns:
{"QueryResult": {"_rallyAPIMajor": "2", "_rallyAPIMinor": "0", "Errors": ["Could not read: could not read all instances of class com.f4tech.slm.domain.PortfolioItem for class PortfolioItem"], "Warnings": [], "TotalResultCount": 0, "StartIndex": 1, "PageSize": 20, "Results": []}}
This type of filtering works with all other types of custom fields. There must be something different with the way custom User dropdown fields are implemented in the backend?
Release : SAAS
Instead of: Parent.c_UserDDL = "XXX". Where XXX is the internal user number.
use: Parent.c_UserDDL.UserName = "UUU". Where UUU is the user's User Name.