RELATED IDEAS
Allow to define a default release for new Features
We create a lot of features via the New Feature dialog. All these features are assigned to the Parking Lot release. Aha uses the first real release in the list as selected default entry.
It would be much better, if we could configure, which release should be the default, e.g. the parking lot, so that it is not necessary to select a different release all the time.
-
ADMIN RESPONSENov 1, 2022
You can now set a default release for newly created features and epics in the Settings > Workspace > "Configure" page. The new setting is named Default release.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
Received this email today, where can I set the default release for new epics?
-Kent
Hey team, on the release default value, If configuring is not an option could you stop defaulting the release and make the user select it please?
I would understand the flow if it chose the latest release for the initiative I am working in but it chooses the first release in the list regardless of the initiative is linked to, so I then have to hunt for the feature/story and change it anyway, so the default is actually more work than me selecting the release I want in the first place.
Yes, that's what everybody is waiting for!
Any updates on this?
Is there anty update on this? How is it that we can define a Template for a feature, but not a default release?
Yep, agreed that defaulting to parking lot is more logical and time-consuming to have to switch the release every time.
Yep - need this; major click requirement with this not existing. When we create a feature, we don't always know which release it's going to be in, so we put it in a parking-lot until the cycle is defined. This requires like 2 extra clicks for every feature. I have thousands of features in our backlog.
Any update on this? can the default be changed to the parking lot as a first step with ability to define the default release a later feature?
I'm shocked that this feature doesn't exist already. This would be a great feature to have in order to help facilitate and manage cause not everything can be committed and like most organizations, there is more work to do then can handled at one time.
+1 for this. I'm really surprised this isn't an option particularly when the parking lot (i.e. backlog) exists. Adding work to an actual release should be a conscious act. It'd be very rare in our world (and I think elsewhere) that a newly added feature would automatically make it into the next release.
This would be incredibly helpful for me! I often forget to change the release when creating a new feature.
Yes. It would be very useful.