When copying a feature, carry over the to-dos

Duplicating a Feature List card should duplicate its To-dos with options to include/exclude assignment, deadline, comments, etc. Otherwise add a function to duplicate To-dos into a new card, with options to include/exclude assignment, deadline, comments, etc.
  • Suzanne Vaughan
  • Mar 20 2015
  • Shipped
Release time frame 1 month
  • Attach files
  • andrew robles commented
    13 Mar, 2017 10:38pm

    This is a great idea that my team could really use.  I wanted to check in see if this Idea has been implemented yet? If not, when can we expect to see this feature to be added? 


  • Melissa Labrecque commented
    9 Feb, 2017 05:52pm

    Please please can we get this implemented????

  • Melissa Labrecque commented
    9 Feb, 2017 05:51pm

    Hello, can we please, please make this a priority???

  • Elliot Green commented
    4 Oct, 2016 12:29pm

    This will greatly help us when creating templates for marketing campaigns.

    Our marketing activities are expressed as features and this is what we predominantly want to duplicate.

    At present we have to copy releases with their subsequent features to copy over the to-do's which is a slightly clunky process.

    It would greatly help if we had the capability to copy over features and their to-do's as these are required to get campaigns signed off 

  • Melissa Labrecque commented
    29 Jul, 2016 06:15pm

    We have created and in order for us to copy a feature, instead of cloning entire release, it would be SO helpful if we could copy the feature and have it copy the to-do’s. Please!

  • Guest commented
    19 Feb, 2016 04:56pm

    FYI - the ideal scenario would actually be the ability to create templates from existing cards - or to just be able to create full-fledged templates in the "Custom workflow type" section. Right now we're limited to just a description box. I would love to be able to add to-do's, tags, watchers etc. into a template which I could then create within a lane. The solution outlined in this idea is really a workaround for that which appears to have less friction.

  • Guest commented
    19 Feb, 2016 04:50pm

    Hey Chris - thanks for your question. For my purposes, the duplicated to-do's could stay the same as I have built a series of template cards to copy from (all to-do's in those are in-complete). In our case the assignees should definitely stay the same after being copied as the tasks we built out are done by the same people over and over (design review, for example, is a to-do consistently handled by one individual). 

    We may be a somewhat unique case as we're using Aha as a marketing team (it was sold to us as being a competent PM tool for marketing - which it mostly has been). Lanes in the features section are weeks, and feature cards represent projects. I believe your marketing team has their board setup this way. We have set campaigns/projects which we run on a monthly, weekly, or sometimes even daily basis. All of which go through exactly the same workflow and process - mostly represented by to-do's. We run a series of e-courses, for example, that all go through the same workflow to be created and marketed. These have been templated for speed and consistency. We go back and tweak the templated cards as we improve processes and efficiencies for executing project/campaigns.

    This feature addition is one of many, many improvements which I have in mind that could transform aha into an incredibly powerful marketing management tool. I'd be happy to hop on a call to explain further if you'd like to do some research. Thanks!

  • Admin
    Chris Waters commented
    19 Feb, 2016 04:34pm

    If a feature is copied should the duplicated to-dos be reset? e.g. should each completed to-do be marked as in-complete? Should the assignees be removed so the new to-dos can be assigned to different users?

    Can you expand on why you are copying features? It would help us understand why duplicating the to-dos would be useful too.

  • Guest commented
    19 Feb, 2016 09:49am

    This would be incredibly useful! We would use this function on a daily basis and it would remove one of the major pains we're experiencing in the software right now.

  • Guest commented
    22 Mar, 2015 06:07pm

    A polling function for resolving team decisions, each member being assigned a radio input indicating pending/affirmative/negative (pending/agree/disagree), with expandable/collapsible comments as supporting reason.

    Tks & Rgds.

  • Admin
    Suzanne Vaughan commented
    22 Mar, 2015 01:36pm

    Can you expand? A polling function for what? I can update the description accordingly. 

  • Guest commented
    20 Mar, 2015 12:15pm

    Thanks for helping create this Idea, Suzanne. I actually intended to use To-dos as a polling function with its comments as supporting reasons. So it works as well if Aha! comes up with duplicable poll templates.

    Best Regards.

  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e