Default Release Phase

You should be able to set at default release phase for a release, so that all features added to this release ends up in the default release phase. This would gratly simplify and make the prosess more efficient. Now you have to move new features into a relesephase after creating it, and it does not show up in the releases details view timeline before you do so. 

  • Odd-Henrik Aasen
  • Dec 11 2015
  • Unlikely to implement
Release time frame
  • Attach files
  • Admin
    Ron Yang commented
    December 12, 2015 01:22

    Thanks for the idea. Did you know that you can bulk add existing features to a specific release phase? This is a very easy and efficient way to get your existing features into a specific release.

    By going to the Releases roadmap screen and clicking on +Existing features, you will have ability to add all features in the release to the release phase of your choice.

    At this time, we do not have plans to default features into an existing release phase but we hope that the mentioned workaround will continue to allow you to use Aha! in an efficient manner.

  • Odd-Henrik Aasen commented
    December 14, 2015 13:30

    Hi, Im aware of the bulk edit feature. + Existing features helps some. But its still cumbersome. Having the +New feature underneath all phases would also help. 

  • Leila Pearson commented
    October 10, 2018 13:13

    I'm surprised that this feature isn't being requested by more people and that it is shown as unlikely to implement. Perhaps my workflow is strange somehow and someone could suggest how to change it?

    My release template includes 3 phases - Specification, Development, and Delivery. 

    All features that I create need to be added to the Development release phase. Without some way to specify the default release phase for features this means I have to manually set the release phase for every new feature that I create in Aha and for every feature that I import from Jira. Yes, I can do this in bulk if I have a bunch to change, but it's still manual. Also, the more common case for me is to add features one at a time to a release rather than in bulk. 

    What are other people doing that they don't have a similar issue?

    One workaround might be to give up on having a Development release phase at all - but then the roadmap view looks weird since all of the features are shown below the last phase which is Delivery and really Delivery should be shown last. 

    Another workaround would be to use features for the specification and delivery phases - but I actually want them to show in different colours as different groups own these phases. I know I can colour based on assignee/owner but that doesn't seem quite right here either...

    Neither workaround seems acceptable to me.