Skip to Main Content
Status Already exists
Categories Releases
Created by Max Cascone
Created on Aug 19, 2015

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.

  • Attach files
  • Max Cascone
    Reply
    |
    Sep 16, 2015

    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]

  • Suzanne Vaughan
    Reply
    |
    Sep 15, 2015

    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
    Reply
    |
    Aug 19, 2015

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

     

    Launch == Release