RELATED IDEAS
Ability to create a new release without a release date defined
When you create a new release, you have to populate a release date. Often we create releases ahead of release planning and when dates aren't agreed. By having to populate a release date, this causes confusion as some people think the date is agreed. Would like to be able to have a blank release date.
1
MERGED
Releases Shouldn't Require Due Dates
When creating a release, if I don't set the release date, it automatically sets the release date to today. I would like to be able to plan a release, assign work to it, before I set the due date. What happens now is once we create the release, we ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
We also need parking lot releases to have no release date. Aha sets a release date of a parking lot release to 1 month after it was created. This can't be changed in the UI or even set to NULL in the API. We need parking lot release to have NULL for their release date. We have automations for features to sync their custom GA target date with the release date. When a feature is moved to a parking lot release the feature's custom GA target date is being set to that release date in the past incorrectly. It should be set to NULL instead since parking lot releases are backlog release buckets and shouldn't have a date and thus features in them also shouldn't have a GA target date.
Hi Nathaniel, correct! We only want to assign a release date, once the release date is agreed. But currently, we have to populate a date which causes confusion.
Thanks for sharing this idea! Quick clarifying question: are you looking to create a non-parking lot release without a date?