Geek Answers Handbook

RALLY: determining the parent version of User Story

In the rally, we have the following structure of history:

Parent story 1
| __ Sub Story 1
| | __ Children's story 1
| | __ Children's story 2
|
| __ Sub Story 2
| __ Children's story 3
| __ Sub Story 3
| _ Children's story 4

I want to see all the parent stories and what release is currently planned. After the parent story has children's stories, the meaning of its release is not edited because it is set in a lower story. Is there a way to determine that a release will be completed by only making 1 rally call?

Thanks!

+4
source share
2 answers

The easiest solution I found is to do the following:

var epicLevelStories = { key: 'epics', type: 'hierarchicalrequirement', fetch: 'FormattedID,Name,ObjectID,Release' query: epicQuery, order: 'FormattedID' }; var epicLevel2Stories = { key: 'epiclevel2', placeholder: '${epics.children?fetch=Name,FormattedID,Parent,Release}' }; var epicLevel3Stories = { key: 'epiclevel3', placeholder: '${epiclevel2.children?fetch=Name,FormattedID,Parent,Release}' }; var queryArray = [epicLevelStories, epicLevel2Stories, epicLevel3Stories]; rallyDataSource.findAll(queryArray, doStuffWithResults);

Once you get a result set (epiclevel #) that has no entries, you know you have reached the bottom of the tree.

I assume that if epiclevel3 still has stories, then you can build a new array of queries for the next 3 levels and recursively call the same doStuffWithResults method. Just a thought. I have not tested this.

+2
source

If you want to get a list of parent stories to see which release they are in, you can use the following query.

(Parent.Parent.FormattedID = ###PUT THE FORMATTED ID HERE###)

If you want to experiment in your browser, you can try the following URL.

https://rally1.rallydev.com/slm/webservice/1.26/hierarchicalrequirement.js?query=(Parent.Parent.FormattedID=###PUT_THE_FORMATTED_ID_HERE###)&fetch=Release&pretty=true

If you knew that stories about children would be in one issue, you can put & pagesize = 1 and watch the issue for this one returned story, while maintaining a small bandwidth.

One of the weird parts of this query is that you will need to know how deep the stories you want to get from the parent you are interested in. In the case of your example, your hierarchy has two depths, so in the query you use Parent.Parent from the stories I'm trying to get.

+4
source

More articles:


All Articles