RELATED IDEAS
Automation rule to set feature start date to same as release
Current automation rules allow for a start date to set to an increment from today(). It would be useful to have automation that would update the start date of a work item to the same as the release start date for capacity planning purposes.
Additionally it would be useful to be able to set the due date to an increment from start date rather than from today or even better due date as a calculated value from today based on the original estimate and a defined value.
1
MERGED
Add automation to set Story Dates based on Release Dates
Who would benefit? People who calculate Epic Dates by Story Dates What impact would it make? My roadmap would update automatically to reflect the dates work is happening How should it work? I should be able to create an automation that says, 'When...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
We have multiple use cases where we want to trigger on a change to a record and then update a field for that record based on a value of a related record's field. We see value in opening this up and allowing access to update a particular record's field value based on values in other record fields of similar type. This would make Aha's automation very powerful! Besides the use case above we also have these as well:
When a feature is moved into a release, allow the Feature's custom field date (e.g. GA target date) to be set to the related release's external release date.
When promoting an idea to an existing feature we want to set the idea's status based on its related feature's status. We have a mapping between these status and want to build this automation to save PMs manual effort.