Hello Ralph,

Thanks for addressing my question , i hope you also went through my second question which co-related with this question, hope at least my both the question question is clear

So i will first touch on what is our business problem :

The main of purpose of this is to give overall summary of Code Review like No. of Issues , How many are fixed for given Delivery , as you are aware of latest changes which was done in ELM 7.x , the UI of code review section was changed ,along with which our existing tool which was doing the job to generate the report got deprecated and now we are again trying to re-gain the working functionality of the tool , basically we are providing all data of code review like (Code Reviewers, status, code review status , review cycle ,no. of files modified,....) under a csv file which further on taken up by respective team to perform their process

Now how our tool works :

I never mentioned that i am trying to fetch the list of all task from repository ,my tool flow is quite simple

Go to Delivery workitem -> fetch the linked change request -> iterate through each Change request and get the linked story -> iterate through each story and get the list of task now once i have the complete list of task here just to shorten the execution time (my second question comes into the picture) here  from the list then we will identify which workitem has code review and which workitem does not , workitem that have code review we furthur store it in some collection and then we will pass the list of task worktiem(now here it could be 10 task or 100 task as well depending upon development team how many implementation task they have created for the given delivery) separated by comma as scm command to get json which we will further parse into readable csv format

Hope i clarified my point :)