Skip to Main Content
Status Shipped
Created by Suzanne Vaughan
Created on Mar 20, 2015

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.
Release time frame 1 month
  • Attach files
  • Guest
    Reply
    |
    Mar 13, 2017

    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? 

    Thanks

  • Melissa Labrecque
    Reply
    |
    Feb 9, 2017

    Please please can we get this implemented????

  • Melissa Labrecque
    Reply
    |
    Feb 9, 2017

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

  • Guest
    Reply
    |
    Oct 4, 2016

    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
    Reply
    |
    Jul 29, 2016

    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
    Reply
    |
    Feb 19, 2016

    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
    Reply
    |
    Feb 19, 2016

    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
    Reply
    |
    Feb 19, 2016

    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
    Reply
    |
    Feb 19, 2016

    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
    Reply
    |
    Mar 22, 2015

    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.

  • Suzanne Vaughan
    Reply
    |
    Mar 22, 2015

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

  • Guest
    Reply
    |
    Mar 20, 2015

    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.

4 MERGED

Add defaults to-dos to features

Merged
When creating a feature, I want a set of canned to-do's added to the feature of a certain type, so I can ensure certain planning steps are completed.
Guest about 8 years ago in Features 0 Shipped