Do not cascade status to parent work items

Do not assume that when the last requirement has been completed that the feature is complete.  Allow me to set the status of pare.  Just because it's the last requirement on the board doesn't mean it's the last requirement overall.  Today, when the last requirement is done, the parent feature status is changed to done.  Interestingly, if there is a master feature, it's status is not changed to done when the last feature is done -- and I agree with this behavior.  With the new ability to define separate workflows for master features and requirements, this idea becomes even more useful.  With integrations to other solutions, such as TFS, I may not notice that a requirement status has been updated and may not notice that the feature status was changed.

I think I may have either submitted this idea before or at least voted on it, but I cannot find it now.