RELATED IDEAS
Auto calculation of feature dates
It would be useful if the start and end dates of a feature could be auto calculated, so that once placed in a release and linked to any dependencies then the dates should not require any other changes. This would make both the planning of dates and also the tracking of dependencies easier.
This would be based on the following rules:
- The feature should not start before the start of the release date that it is assigned to.
- The feature should not start before the end date of any feature it is dependant on
- The end date should be set from the start date plus the estimated time to completion
In addition to this if the end date falls out of the dates of the release it's in then a warning (symbol, colour coding etc) should be present to all a user to identify this.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
I agree that setting feature dates based on the release they are placed in would be a very valuable feature. This is something we are struggling with in using Aha. If items are in the parking lot, then maybe no dates are associated, but if pulled into a release then they default to the release dates assuming the release is set to a future date or that no dates exist within the feature. This would allow you to change the dates in the current increment based on effort not spanning the entire release.... if you choose to do so. It would also allow for dates getting updated when you move to a future increment release.
Same issue as Maxime below. We have two-week sprints, and each time a sprint concludes or priorities change, features are moved to new sprints. We have to remember to check and modify dates that are out of line with the release else our roadmap is not correct.
Yes please the ability to default the date range based on the release dates would be a huge time saver.
In our case, we use the releases to represent the "development sprints". If a feature is in a release, we would like the feature start date and feature end date to be set with the release start/end date.
The end goal is to be able to show the initiatives dates based on the features that they contain.
I saw that we could configure initiatives to calculate their dates automatically based on the features and epics...However, since our features don't have the right dates (the releases do), we're stuck...
I respect how complicated this is from a development standpoint, but would really add a lot of power to Aha!
This is important. To utilise Aha properly in the organisation, I have to ask product owners to change their current process to add start/due dates in Jira, so they appear on a Release Gantt in Aha. Having these dates set when a feature changes status to, eg, In Progress would be a great help.
YES! I tend to place something on the roadmap with the knowledge of start date & estimated duration. If Aha could then calculate the end date for me, it would make my brain have to work a little less.
Would love to see the power of MS Project (related to dates that tie together, i.e., push out the date on one deliverable then those deliverables impacted will have their due dates pushed out) within Aha as well.
This is similar to a similar request posted almost a years ago "Updating of Feature dates should automatically adjust dates of features with downstream dependencies". I suggest you vote for that idea as well.