"Deployment Task" tab defaults to the "Not Started" execution run instead of the current run

ID:    D23197
Published:    04 March 2016
Updated:    26 April 2017

Defect Id


Originally Reported Against

Release Manager

Resolved In

Release Control 6.2


If there is a parent and child release package linked together and the parent had a failed deployment attempt, after the second attempt, the child release package will default to the "Not Started" run associated to the first failed deployment attempt.


Workaround: use the drop down on the "Deployment Task" tab to choose the correct deployment execution attempt.

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs