We have a scenario where we don't want Devliery Stages to auto-complete, but the only way to manually control when a stage is completed is via script.

by: Kiyotoshi I. | about a year ago | Templates & Releases

Comments

• Thanks for sharing this idea. We’ll look into its feasibility in the upcoming months and review it further based on customer upvotes.

  by: DevOps Product team | 11 months ago

  official response

• Bump, also going to add a little more detail to help:
  
  We have a "master template" that generates sub-releases. Each release can have 1 or many applications being released under it, so we register all the tickets from all the applications being released to one Delivery. We could register copies of each ticket with a unique Tracked Item name, but our QA would like to keep the clutter down. Also, you can see all the releases associated to that Tracked Item and that's fine for our QA to keep track of which sub-releases have completed that phase. If we enable auto-complete when all Tracked Items are completed, there may be a sub-release that is stalled for any reason but the Tracked Item will be marked completed from another sub-release (we also have tickets shared between applications if the fix spans multiple apps) and the phase will be marked completed and closed. The sub-release that was stalled will continue foward but fail because the phase has been closed and you can't act on a closed phase.
  
  I hope this helps give some insight into why we would like this feature.

  by: Kiyotoshi I. | 4 months ago