Derive the Master Feature Release(s) based on Child Features

It'd be great if I had an option to have the system derive the release(s) that a Master Feature belongs to based on the release(s) that the Features that tie up to the Master Feature are slotted in.  This would include the ability for the master feature to span across more than 1 release.  I'm currently running into challenges with deciding which release to slot the Master Feature in (realizing the general recommendation is to align it with the release that contains the last feature).  Right now I'm considering copying the same master feature over into multiple releases but that just seems like it is adding a lot of bookkeeping for not a lot of payoff.  After all, we are delivering pieces of the Master Feature in earlier releases, just not the complete Master Feature.

  • Guest
  • Feb 12 2018
  • Future consideration
Release time frame
  • Attach files
  • Daniel Haisley commented
    April 17, 2018 12:19

    Yes to this! I'm running into the same issue where I need to have master features (think components in Jira) span multiple releases, but can't. As a workaround, I'm versioning the master features, but this is suboptimal as it breaks the reporting capabilities that drive the entire use-case around master features to begin with. 

  • Matthew Reed commented
    June 29, 2018 15:08

    Put Features under your Master Feature and associate those Features with their correct release. Then move the Master Feature to the Release that contains the last Feature completed.

  • Jerimy Gregory commented
    July 11, 2018 00:20

    Master Features should be able to span multiple releases and as others mentioned, it would be magic if the children features helped drive the release timeline so that you could show a master feature will span multiple quarterly releases.