Support release templates for master releases

When using master releases, it is not possible to select the release template for the sub-releases to be created. Which means the workflow to date looks like this:

  • Create a master release
  • Resist the temptation to select the products in the product line, as creating a release here would use the (wrong) default template
  • Go to each product and create a new release, using the desired release template
  • Then go to the master release and attach the newly created release for each product in the product line

This process is more tedious the more products you have in a product line and could be smoothed up significantly by allowing the selection of a release template in the master release creation dialog.

  • Guest
  • Sep 1 2015
  • Future consideration
Release time frame
  • Attach files
  • Stephen Morse commented
    6 Jun, 2019 04:17pm

    I wanted to check and see if there has been any further consideration of this Idea.  It is incredibly time-consuming to rebuild the Master Release with each new one.   We control the majority of our activities from the Master Release.  IT feels like the Master release is pretty much an afterthought.  Anything that AHA can do to get his moving would be great! 

  • Eva Altass commented
    26 Jun, 2018 12:21am

    At present I need to manually add phases or try and copy them for master releases - other releases have a template, would be nice to be given the choice to select a template or not when creating a master release

  • David Millward commented
    21 Apr, 2018 06:41am

    Would be very useful as we often link multiple products in a release

  • Guest commented
    22 Feb, 2018 03:40pm

    It is important to understand that even though you have sub-releases, when they are tied to a master release, the master release will have its own program activities to track that are independent to the sub-releases.  Today, the master release doesn't provide you with this concept, as currently implemented it provides you with a grouping.  This can be achieved today by linking different product releases together.  Please consider moving this from likely to implement to planned.  It would be great to get this feature enabled in the next few weeks.

  • Kevin Burges commented
    7 Feb, 2018 01:46pm

    I agree with a previous comment that there are two distinct things needed here:

    - allowing a master release to use a release template
    - allowing the sub-releases to be created with a specified (or default) template

    Both are useful but the first is most important to me as there is no workaround for it other than to manually create the release phases from scratch each time.

  • Zach Novak commented
    8 Jan, 2018 04:45pm

    We have quite a few process steps involved with each of our Master Releases that I'd love to have a template for.  Otherwise, each time I create a new master release, I have to recreate the process each time. I've also tried to find a way around this issue by using a bulk upload; however, Master releases cannot be loaded via CSV.

  • Jasper Diephuis commented
    6 Dec, 2016 03:13pm

    Perhaps it is better to separate these two ideas in two separate ideas in the portal as well?

  • Jasper Diephuis commented
    6 Dec, 2016 03:04pm

    I voted for this issue because of the title although I think there are 2 very different requests related to this title:

    1. Support of release templates for master releases. Which would allow me to configure all phases common to all master releases. 
    2. Support of release template selection for all sub releases when creating a master release. This would prevent the situation which the creator of this idea has described. 

    I'm actually interested in both, but mostly in 1 because our master releases contain quite a number of phases which I have no choice but to manually create every single time.

  • Sean Connelly commented
    1 Jun, 2016 07:46pm

    This actually confused me. I was mid drafting an email to support, but checked here to see if anyone else had noticed this. Thought it was a funky bug or problem with how I was doing things. Would be valuable to my company for alignment purposes. I'll just forego using the release template for now, or try to see what extra value would be gained out of using Lars' suggested workaround.

  • Admin
    Ron Yang commented
    13 Apr, 2016 09:05pm

    This idea has been marked as Likely to implement -- which means that we agree that this is a good idea but timing is TBD. It has not yet reached a point where it was been prioritized (relative to other items in the existing backlog and roadmap). Please stay tuned, and as updates occur, we will update the status and release time frame.

  • Guest commented
    13 Apr, 2016 09:19am

    Any idea when this feature is likely to be implemented?

  • Guest commented
    13 Apr, 2016 09:18am

    If I select the sub-releases when I create the Master Release, it should pick the default release template associated with the product and apply the same

  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e