<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8"> </head> <body> <div style="font-family:sans-serif"><div style="white-space:normal"> <p dir="auto">On 30 Sep 2016, at 7:24, Ranjith Varakantam wrote:</p> <p dir="auto"></p></div> <div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir="auto">On Fri, Sep 30, 2016 at 1:22 AM, Leonard Dimaggio <ldimaggi@redhat.com> </div><div dir="auto">wrote: </div><div dir="auto"> </div><blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><div dir="auto">Ranjith, </div><div dir="auto"> </div><div dir="auto">When you say: </div><div dir="auto">'...If yes, would it get incrementally updated along with each of child </div><div dir="auto">work item?...' </div><div dir="auto"> </div><div dir="auto">Are you referring to a state change in a child element resulting in an </div><div dir="auto">automatic state update in its parent element? </div><div dir="auto"> </div></blockquote><div dir="auto"> </div><blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><blockquote style="border-left:2px solid #777; color:#BBB; margin:0 0 5px; padding-left:5px; border-left-color:#BBB"><div dir="auto">Yes, for example a user story has 4 tasks, when these tasks are </div></blockquote></blockquote><div dir="auto">complete, the user story should automatically be marked complete. The same </div><div dir="auto">would hold good for experience, if the user stories related to the user </div><div dir="auto">stories are complete then the experience state should also change. </div></blockquote></div> <div style="white-space:normal"> <p dir="auto">this assumes you have captured <em>everything</em> in all tasks and upfront knows nothing else are there.</p> <p dir="auto">I would not think automatic changing state to complete is the right thing to do.</p> <p dir="auto">Being able to list issues which have all their children and dependent issues resolved so<br> one can make an explicit decision - <em>thats</em> useful.</p> <p dir="auto"></p></div> <div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><blockquote style="border-left:2px solid #777; color:#BBB; margin:0 0 5px; padding-left:5px; border-left-color:#BBB"><div dir="auto">This would also inline with the query based results that Todd suggested, </div></blockquote></blockquote><div dir="auto">because when I am refining the backlog, I only want to see the experiences </div><div dir="auto">or user stories that are yet to be worked on. i.e. the ones which are not </div><div dir="auto">completed. </div></blockquote></div> <div style="white-space:normal"> <p dir="auto">Yup - but that query should be done by query and stories going into the state of being in progress,<br> not about amount of child tasks it has IMO.</p> <p dir="auto">/max<br> <a href="http://about.me/maxandersen" style="color:#3983C4">http://about.me/maxandersen</a></p> </div> </div> </body> </html>