Restricting scope of the "Feature Progress Measure" (SAFe advanced Report)
Hello,
Accepted answer
Hi Olivier,
I'm about to post updates to the reports, this one included, that add the filtering you're requesting. In the mean time, you can simply add on of these two columns to your result set (and make sure you include the additional column in the GROUP BY clause):
T2.TEAM_NAME
T2.REQUEST_CATEGORY_NAME
Please let me know if that resolves your question.
Amy
Comments
Hi Amy!
Thanks a lot it helped.
In the SQL of my report, I had to mention T1.REQUEST_CATEGORY_NAME (not T2).
I also did not need the team name since I'm limiting the scope of the features based on the "Filed Against" field.
In addition, I wanted to restrict the scope for those of a given PI (and its "child" iterations). As I forgot how to work with inner/outer joins :-), in the WHERE clause I had to specify the id of the iterations something like this...
(T2.REQUEST_CATEGORY_NAME = '99. pmo') AND
(T1.ITERATION_ID = 17929 OR T1.ITERATION_ID = 17930 OR T1.ITERATION_ID = 17931 OR T1.ITERATION_ID = 17932 OR T1.ITERATION_ID = 17933 OR T1.ITERATION_ID = 17934 )
2 other answers
Hello Amy,