Is any way to add a template for adding to-dos in Aha?
We will use same template for add to-dos in Release Phase. Now, we have to add the to-dos under each Release Phase manually. If a project manager have many products and each release phase has same tasks need to be added in. That will be a huge job for adding the same tasks.
So do you have an idea to create a template for adding to-dos or add bulk to-dos?
Release time frame | 3 months |
This would be extremely beneficial for our teams.
Agreed with the June 2016 comment on adding To Dos to the Release templates. We had a great team meeting yesterday and this topic came up. During the creation of some Release templates, we realized that a To Dos engine (like in Features) could be added between Default Description and Type in the "Edit Release phase" box. Additionally, if the bullet points in the attached image were To Dos (in our case they would be), we would've put those in as To Dos.
Even if the owner and due dates weren't saved in the templates, it would still save a lot of time every time a release template is utilized. In our specific case, and we're guessing in many other companies, we would use a Launch/GA checklist for the To Dos in a template.
Lastly, if the existing To Dos engine is used for this new field in templates, it would show up in My Work which is necessary.
It sounds like the other way of doing this is to create a release as a template and add the to-do's manually to the phases, then copy the release template for future releases. This would be a workable solution, however another user that is doing this commented that the to-do's get copied in reverse, so you lose the order they were setup in.
Wanted to bump/upvote this. There are a series of tasks we want Product Owners to sign off on before an effort is moved into "Ready for Development." We would like to configure these at a template level and have them automatically assigned to the issue/initiative owner. Ideally the following features would be included:
Ditto Jonathon Leeke...
We also need this to help default in owners for tasks throughout our regular release cycles. This would save a lot of time in the setup. ToDos for release milestones are used to create a virtual checklist of items to be completed.