move release (launch) to another product

Our Aha work was put in by someone who didn't really understand the tool, and some launches are not associated to the right products. It seems the only way to move these launches is to create a new launch in the right product, and manually move any associated features into that new launch. It would be more efficient to allow moving the launch wholesale to the new product, taking along all features and other data with it.

  • Max Cascone
  • Aug 19 2015
  • Already exists
Release time frame
  • Attach files
  • Max Cascone commented
    August 19, 2015 22:07

    Sorry, we call Releases "Launches" where I work.

     

    Launch == Release

  • Admin
    Suzanne Vaughan commented
    September 15, 2015 20:24

    Hi Max -- you can do this today using another capability for cloning releases (launches). If you clone an existing launch from the correct product, it will take all of the features, requirements, to-dos and copy them over. I'd give that a try before manually moving them. The other benefit is that the object IDs are newly created to match the correct product. 

  • Max Cascone commented
    September 16, 2015 22:38

    That’s good to know, thanks!

    Max Cascone
    Associate SW Project Manager
    550 W. Van Buren Street
    Chicago, Illinois 60607
    Office 312-880-3157
    mcascone@huronconsultinggroup.com
    www.huronconsultinggroup.com
    [Huron Legal]