Update status of requirements on status change of feature

I don't want to change the status of each and every requirement individually when changing the status of a feature.  For example, when I hand off a feature - which has 5 requirements, for example - to engineering to spike, they come back with a full estimate of the feature and all the details on how they are going to satisfy each requirement.  I review and accept the estimate.  Now I have to go to Aha and update each requirement's status *and* the feature status to push the feature into the next phase of the workflow.  I would like to set up a rule/flag on each status that says something like "when entering this status, all requirements will assume the new status also."

  • Guest
  • Jun 29 2015
  • Unlikely to implement
Release time frame
  • Dec 23, 2015

    Admin Response

    Status changes on features and requirements are purposely designed in this way to ensure that all requirements are fully ready for the next status. Because a status change is a major "event" for the requirement or feature, we feel that it should be actively done (so that requirements are not forgotten).

    At this time, we are unlikely to make changes in this area based on current priorities. We hope you can understand.

  • Attach files
  • Michal Anderson commented
    October 23, 2015 15:37

    I'd maybe suggest the reverse, when  all the requirements of the feature are updated then update the feature to a new status. 

  • Shri Iyer commented
    April 14, 2016 19:29

    I have a feature that has 20 requirements in it. After implementation, I mark the feature as Shipped. However the system does not mark the requirements also as shipped. I don't want to individually update all 20 requirements manually. At the least, the system should ask me while updating the feature status, if I want to also update all the requirements with the same status.

  • Scott Bleasdell commented
    August 16, 2016 20:12

    I agree with both comments listed above, but also Aha's position on the matter.  It is best practice to update the status of a requirement from "Under Consideration" when the definition of the requirement has been completed.  That should be a "manual" process.

    However, in cases where all of the requirements are marked as "Ready for Development", for example, the feature status should reflect that by automatically updating accordingly.

    Additionally, for certain feature status changes - most notably being set to "Shipped" - the status for each requirement should be updated (in this case to "Shipped" as well).  I can't think of an other feature status change that would trigger this type of bulk update to requirements, by the way.

  • Max Cascone commented
    December 21, 2016 16:53

    You could probably bulk update them by building a report of the items you wanted and using the bulk edit feature. Not the quickest thing to do, but it would work.