It's all about the answers!

Ask a question

How are Deliverable attributes accessed when returned as an itemValue?

Mitch Slater (153) | asked Aug 25 '22, 12:15 p.m.

 I'm attempting to grab a Deliverable type custom attribute for defects, but am having a hard time getting the information from my query. My query currently looks, in part, like the following:


I'm close, but the <itemValue> tag inside the <allExtensions> tag does not have any content in it. I assume I need to specify the attributes of itemValue I'd like to see, but I haven't been able to find any documentation on what properties are available. I've tried accessing Deliverable attributes (like querying itemValue/name), but haven't had any success yet.

Any ideas on how I can access the Deliverable attributes that the custom attribute's itemValue are pointing to? Thanks in advance!

2 answers

permanent link
Ralph Schoon (62.7k33643) | answered Aug 26 '22, 4:32 a.m.

 This shows the details of a deliverable:

It should be the same, regardless of the built in or a custom attribute. The issue seems to be to get the custom attribute. I will try to have a look later.

permanent link
Ralph Schoon (62.7k33643) | answered Aug 26 '22, 7:15 a.m.
edited Aug 26 '22, 7:17 a.m.

 Mitch, take this with a grain of salt, as I am not an expert in this reportable REST API. 

I had a look at it here: and looked at your question. I spent some time looking at it on my test system and here what I found:

I create two custom attributes. One a small String and one ID of type deliverable.   

If you use the Reportable REST API to get the work item ID, Summary and Planned for, you find that there are a lot of details in the Planned For attribute (target). E.g. use

For target I get a bunch of attributes that I can access e.g. a name. 
allExtensions returns(I believe) all data available for all custom attributes. 

If I do this, I get for target (replaced brackets with [])
            [name]Sprint 2[/name]
            [id]Sprint 2[/id]


And for the specific extension I get:

Apparently none of the interesting values are available for my custom attribute of type deliverable. So it looks as if that information is not provided, not even the display value, which is empty, whereas for the built in attribute (target) you get all you want.&nbsp; For the string extension, you get more data but it is a way simpler object as well.

I am not that knowledgeable in this API and I might be missing something, but to me it looks that the custom deliverable attribute is not fully supported in the reportable REST API. 

It might be better to try the OSLC API. In that API you get a link to the deliverable

which you can follow to get the full data about the item (I checked). Unfortunately you have to deal with the complexity of OSLC Queries and OSLC in general.

Ralph Schoon commented Aug 26 '22, 7:28 a.m.

The forum software massacred my answer a bit. e.g. in the second link there is an asterisk missing in the () at the end. 

This is the URI selecting only the custom attribute of type deliverable (I messed up the Display Name and the ID...)[id=240]/(id|summary|target/(name)|allExtensions[key='']/(*))

Ralph Schoon commented Aug 26 '22, 7:41 a.m.

Using itemExtensions does not provide any more details with respect of attributes. example[id=240]/(id|summary|target/(name)|itemExtensions/(*)) 

Your answer

Register or to post your answer.