to-dos in a release template should inherit the phase or milestone dates

The release template concept is great, but the ability to assign tasks to these things is what helps get the work actually done.  You can put a to-do into the release template, but when a release is instantiated on that template, all the to-dos have blank due dates.  They should inherit dates from the phase (end date probably) or milestone.

The workaround is to go through each to-do in a new release and manually set the dates.  This is a pain in a large org that releases every month.

  • Guest
  • Sep 14 2017
  • Future consideration
Release time frame
  • Attach files
  • Scott Bleasdell commented
    17 Jun 13:59

    This seems pretty easy to me for Aha to implement.  Each to-do is associated with a milestone or a phase.  The to-do due date should either be the milestone date or the last day of the phase.  These are already being calculated when the release is created, based on the release date.

    This is important for us because our release process is highly structured, and I'm using to-dos to assign tasks to all involved stakeholders for each phase.  This will ensure that sales gets all their collateral updated on time, and marketing has all their ducks in a row, and even PM has ensured that several required tasks to get the release out the door are all completed, and to-dos give us a way to document all of this activity for every release.  And it would be all automatic, if it weren't for these missing due dates :(.