You just launched a feature whereby you can create a list of to-dos in a feature, and then when you copy that feature the to-dos are copied over with them. However this is a very clumsy way to have to create new features every single time. I need to be able to use the "+" sign within a release etc. Having these templatized to-do's is a great idea, and I would love to use it, but having the only way to use it be to open up the parking lot, find my feature, go into it, go to actions, select copy feature, then change the name, then change the release - that's a very long process flow. We need the add feature window to include a feature template, and that should include the to-do's. I would love to have this - it would make the to-do's actually very usable!
This would be extremely useful for our organization. We have a very repeatable process and SDLC for how are features begin and what is required when handing off something from our Product to Engineering teams. We have a checklist that we review with each item that results in the same To Do Tasks being needed. If we have a way to create a template of To Do tasks that could be reused and added to new features, this would save us an enormous amout of time as well as relieve the stress of worrying that we may have forgotten a To Do that is required.
This has been the biggest pain point in our usage of Aha. We have a repeatable process for what items need done for each feature to ensure a successful launch in a three tiered system depending on how big the release impact will be.
Today, we need to have three "features" that are really just templates, not stored in a way that makes sense (in the parking lot? we use that for other items. In a release? then it muddies our features board). If I'm reviewing an idea that I want to turn into a feature, instead of just promoting it on the spot, I must go to the features board, copy the template that (I hope) ends up being the set of to-do's needed. THEN go back to the idea to promote it. It slows down the review process. <- and this is actually the Aha! suggested path to accomplish this.
It would save us so much time and confusion if we could have several templates to decide which set of to-do's should be included for each feature.
Echo other guests here. With over 100 users on the platform all interfacing frequently in the Aha workflow, having the ability to template to-do / approval list would be a big difference maker
Echoing the previous requests. This would allow us to consolidate our workflow into Aha as a central base of operations, otherwise we get better workflow support with reasonable product management capabilities in other tools.
Lots of votes on this one - any chance this might become part of a release any time soon? Seems its been around since 2017 with future consideration. Would love to know if we might see this come to life.
100% needed. I will add to this as well - allow a standard template of To-Do's to be associated based on the Feature/Activity Type selected when its created. IE - Select a specific feature/activity type and it pre-populates with the pre-built series of To-Do's for that Feature/activity Type.
This would make a big difference in my use of Aha.
PLEASE, we need this. It's one of the biggest things AHA is lacking that would make it perfect. Most companies today need to allow for a consistent and repeatable process. Many things in software development should be repeatable tasks.
This needs to be tied to the feature type as well. A simple text based blob isn't sufficient to ensure a repeatable process.
It would be very welcome!
PLEASE, we need this. It's one of the biggest things AHA is lacking that would make it perfect. Most companies today need to allow for a consistent and repeatable process. Many things in software development should be repeatable tasks.
This needs to be tied to the feature type as well. A simple text based blob isn't sufficient to ensure a repeatable process.
Regarding defaulting to do list for Ideas https://big.ideas.aha.io/ideas/APP-I-6547 It will extremly help us to collect insights from all main stakeholders.
Please develop this feature. Based on this to do list my team would be able to assess if our definition of ready is fulfilled and that we are ready to hand it over to dev team.
This would be incredibly handy for a variety of feature/story types.
Please develop this feature
Will this be slotted into development any time soon? This would be super helpful!
This would be very helpful.
I like this idea very much. We have about 20 to-do's that we add to every feature and this would save a lot of time.