I need a way to get features NOT to determine the length of the phase it belongs to

I need a way to not get features to determine the phase length of the phase they belong to. This is making feature management difficult in the release view.

It is also useful in when Features are mapped as EPICs in JIRA and you do not want due dates on them.

  • Jan Ribe
  • Apr 13 2015
  • Likely to implement
Release time frame
  • Feb 5, 2016

    Admin Response

    As noted, when features are added to a release phase, this will impact the length of the release phase itself. The reason for doing so is that the phase includes the feature (and requires the feature to be completed, before the phase itself can be completed).

    A workaround would be exclude features from releases phases in this view, or to adjust the due dates on features (to match the desired phase length).

    Based on the rationale above, along with current priorities, we do not have plans to make updates in this area. We hope you can understand.

  • Attach files
  • Marc Nield commented
    07 Jun 13:56

    We plan releases and what features (stories) go into them in Jira but Aha doesn't inherit the "membership" of a release from Jira in that it doesn't automatically add the features to a release gantt. When we manually add the features, it simply adds one to the end of the other, extending an already planned release out way beyond the end date and it's a real pain in the neck to put all the stories back where they need to be. In my opinion Aha shouldn't do this, it should allow for the fact that we might "import" a release and it's constituent features, even if they don't have start/end dates.