Need the ability to apply an updated Release Template to a Product

Currently, the Release Template for Phases and Milestones only applies to new releases created and there is no way to apply a Release Template to an existing release, or to update an existing release with a new/updated Release Template.  This would be extremely helpful, as we have created our release Road Map, but are still defining the Phases and Milestones for our processes.

  • cheryl fetchko
  • Mar 7 2016
  • Future consideration
Release time frame
  • Oct 1, 2018

    Admin Response

    As described, the Release template only applies to newly created releases. One potential workaround would be to add a new release, move your features to the newly created release (with your new release template), and remove the old release.

    Applying templates to existing releases is not currently planned on our roadmap, but we will continue to monitor customer feedback here.

  • Attach files
  • Guest commented
    May 26, 2016 17:58

    The workaround described here makes it difficult if not impossible to maintain tracking of status updates for releases, which we'd really like to have throughout the lifecycle of our projects to measure and improve on that lifecycle.

  • Guillaume Etorre commented
    October 19, 2016 13:03

    Feature is vey much necessary so that process and product people can work in the same timeframe.

  • Sharif Alvis commented
    February 18, 2017 17:32

    Agreed that this is an imperative feature. The lack of it severely decreases the ease-of-use of Aha!

  • Thomas Dhollander commented
    July 13, 2017 11:52

    We got started with Aha some time ago and defined quite some releases, that are synced to work in Jira. Our processes are maturing and we are planning to use different release phases / milestones. However, applying these to existing releases turns out to be impossible. It would already help a lot to get the ability to override the full schedule of the release. 

    Thanks for considering this

  • Tom G commented
    October 24, 2017 09:54

    This is the first 'issue' I've come across during my trial of the software. It makes modifying/testing release template changes very painful. I have to remove all features from a release, delete the release, make a new one and put all the same features back in.

  • Ellen Sutton commented
    February 27, 2018 18:02

    Agreed. This is def a pain point for myself as well.  Especially since I sync my releases with Aha, generating Versions.  So to do this workaround, I have to create a new release, sync with JIRA, move features over, delete the other version in JIRA, make sure all the JIRA tickets also move over to the new Version.  All the while trying to not confuse the dev team working off things in JIRA.

  • Julie Edwards commented
    March 6, 2018 14:48

    The workaround is not suitable.  If you follow this workaround, you also need to recreate Comments assigned at the Release level via Copy/Paste. re-add attachments, re-populate release fields etc. which is cumbersome and ultimately impacts the credibility of the audit trail of Comments.


    It would be far better to be able to update a release template and have the choice as to whether the updated template is cascaded to existing in-flight releases or just applicable to new releases.

  • Julie Edwards commented
    March 23, 2018 12:08

    Another reason why this workaround is unsuitable is that where Aha is integrated with JIRA, this will mess up the integration as the JIRA elements will continue pointing to the "original" Release - so everything would also need to be Sent over to JIRA again and remapped.

  • A Hill commented
    September 29, 2018 01:43

    This workaround does not work as we create multiple linkages prior to a parking lot becoming a release.  We use aha to simplify our workflow and eliminate a lot of busy work.  This makes things much more complicated.  Also, we are now seeing the possibility of two different templates (major vs minor releases) and the ability to swap them out would be tremendous. 

  • Julie Edwards commented
    October 1, 2018 15:42

    The workaround also causes problems when existing releases and features have been synched to JIRA.