Skip to Main Content
Status Future consideration
Categories Features
Created by Kody Chappell
Created on Apr 26, 2022

Inherit Start/End dates for Features from assigned Release

In order to use Capacity Planning for teams, we need to have updated Start and End dates on features. With dozens of features to manage and regular changes from one release to another, it can be quite tedious to keep these dates updated correctly. It would be really helpful if I could inherit Start/End dates for features from the assigned release. That way I set the dates of the releases (we release quarterly) and if I move a feature from Q2 to Q3, the dates update accordingly. I imagine this could be accomplished either by a standard configuration or Automation.

  • Attach files
  • Guest
    Reply
    |
    Jul 23, 2023

    We have the same requirement as alot of the comments here. It would be great to have a way to have stories inherit the release that they are put into so that we don't have to enter it manually.

  • Karol Wojciechowksi
    Reply
    |
    May 30, 2023

    Can you provide a specific date for the implementation of this? It would greatly improve the automation of high-level roadmap drawing. Thank you.

  • Ashley Strait
    Reply
    |
    Apr 4, 2023

    Would love to have this! One piece of insight that I shared with our company admin is that we'd love the opportunity to select between manual or automation based on release dates. The epic does this well where we have the ability to select manual dates or feature delivery dates. I got so used to this that I couldn't figure out what was wrong with my features. Such a huge overhead for a program board.

  • Sandy Kobayashi
    Reply
    |
    Apr 4, 2023

    This is the exact capability that we would need. But the current automation limitations don't support it. It would remove some of the mechanical aspects of creating/updating a Feature.

  • Mark Colonnese
    Reply
    |
    Feb 21, 2023

    Would be very beneficial to have this feature. I love Aha! but the absence of this capability is a real shame. It leads to manual re-work and user error if missed; the error then propogating all the way up to the initiative level. Please can this be addressed? Thanks

  • Guest
    Reply
    |
    Jan 26, 2023

    Is there any update on this idea from an implementation standpoint? Could something like this be considered in the next few months?

  • Guest
    Reply
    |
    Jan 24, 2023

    This is critically important feature for our Agile Release Trains & Strategic Planning. If Aha! does not add this soon we may need to move to another tool in 2023.

  • Guest
    Reply
    |
    Oct 25, 2022

    Totally, agree we have the same use case, In addition when looking at Initiatives when their dates are set by Features, it is a pain haivng to change Feature dates when moving between releases

  • Guest
    Reply
    |
    Sep 28, 2022

    I think this is very important feature!

  • +3
2 MERGED

Adding a story to a release should inherit the start of end dates of the release

Merged
Everything we do to drive our roadmap is driven from the bottom up by our user stories. We run on two-week sprints for which we set up releases with start and end dates. When we move a story into a release we have to remember to manually edit the ...
Mark Colonnese almost 2 years ago in Releases 0 Future consideration