RELATED IDEAS
This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-8802 Sync goals between parent and child records.
Improvement: Automatically link a release to all initiatives that are linked to its features
Merged
I as a product owner usually link a feature to an initiative. I'd then expect to see a roadmap on the dashboard where all releases are mapped onto initiatives based on the feature-initiative-links. I do not understand why I should reduntantly link the specific release to the initiatives.
-
ADMIN RESPONSEJul 22, 2022
We are excited to announce a new automation capability for Enterprise+ customers.
Automation rules can be used to streamline a variety of tasks in Aha! and may help with this idea.
In this case you would want to create a feature automation rule like this
When the feature's initiative is changed to 'initiative x'
Then update the release initiatives to add 'initiative x'
A separate rule would be needed for each initiative.
Learn more about automation rules.
We will leave this idea open to consider a more tailored solution for this idea in the future.
28
MERGED
Automatic addition of initiatives to releases based on Features being added to releases that have initiatives
Hi there,
We have recently started using initiatives and they are for sure powerful. One of the strongest features is when you tie an initiative to a release and are able to visually represent when your initiatives are going to be tackled.
I...
2
Likely to implement
I completely agree with the user posts here. Link features to an initiative, then derive the initiative timeline from the releases in which the features are scheduled. Fundamentally, initiatives are fulfilled by a collection of features - NOT releases. Aha! you could take your automation to the next level, and make road mapping much easier.
Yes, would be much more easy, not double down the effort for simple things (and reduce errors).
I agree with this, very frustrating to have to duplicate the effort of linking things. We expect to use Aha to help streamline our process not introduce duplication and potential for errors by missing links.
as a new user this is an obvious one to fix- if you set features with initiatives they should roll up to release and products so initiatives are automatically assigned in hierarchy. to have to add these manually is poor software
Agree with all of the above / manually adding and then maintaining the relationship between releases and initiatives when you have frequent releases is craziness :P
I agree with this. I don't see why it can't pull through Initiatives and Goals to a Release automatically based on the features that are assigned to it (or at least have the option to do that). There seems to be quite a few areas in Aha! where the linkages have to keep being added manually when they should be automated - kind of defeats the point of it.
Similarly when you select an Initiative in the Feature it doesn't automatically pull in the Goals that are linked to the Initiative - I can't for the life of me see why not, it seems a very simple thing to do. Instead you have to manually remember what Goal(s) are associated with the Initiative and add them again - very prone to error and likely just to be missed altogether.
Has anything progressed on this idea? It seems to me that if Aha is really going to help with removing the manual work of roadmapping, it should be able to automatically assign Initiatives to releases based on what features are in the release.
This, used alongside the automatic dates for Initiatives, means that the roadmap would always be correct and updated, so long as the features are tracked in the releases properly. That would be really nice.
As someone who is consulting to clients and helping them to adopt agile practices and use Aha!, this feature is going to be important to adoption of your product. The feedback I receive is that having to update the releases with the increments manually is at best arduous (it takes a while to do) and at worst error prone (if you accidentally miss an initiative, which I have, many times).
I second this. If you have a complex set up of projects and initiatives this is a MUST to see if all Features related to an initiative are actually covered.
If there are concerns that not ALL initiatives should be attached to an epic, perhaps make this a setting that can be configured. But having to constantly do this manually is painful and should be automated.