Distinguish parking lots in automations
Release dates are hidden from the UI on parking lot categories. Automations based on those release dates, however, access these hidden dates and act on them. This means that some automation rules will behave in seemingly erratic because they take into accounts dates that appear to be empty to the users, which causes confusion and unexpected results.
By adding a method to exclude parking lots from automation rules by filtering them out, the rules could then be enacted just when valid releases are used. Currently, that is not possible as the parking lots look just like scheduled releases to the automations.
-
ADMIN RESPONSEJan 13, 2025
To support this use case, we added the following updates to automations:
-
Ability to trigger automation when feature is moved to parking lot release
In the Trigger section, for epics and features, you will see a new option for changes to "a parking lot release".
-
Ability to clear date fields
In the Actions section, you will see a new option for "cleared".
See example below:
Please reach out to us at support@aha.io if you need any further assistance.
-
© 2025 Aha! Labs Inc.•All rights reserved
Thanks for the clarification. Is there a way to exclude parking lot releases from an automation? Here are the use cases:
For non-parking lot releases: When a features' release changes to an non-parking lot release then set it's custom GA target date to it's release's external release date.
For parking lot releases: When a feature's release changes to a parking lot release then clear it's custom GA target date.
For #1, I don't see a way to write this automation rule to exclude parking lot releases. For #2, the date clearing doesn't appear to be working. Please advise. Thanks!
I see this is marked Shipped but no details on how to do this. When I go into my automation rules I don't see a way to exclude parking lot releases.