RElease and overdue sla

[priyadharis]

we have the release with planned end date. When moving from Draft state - release tasks would be created 

when we change the  planned end date on release task , the planned end date of release gets updated but that is not captured in the audit history of the release and the overdue sla doesnt get the breach time updated with new date . when we change the release planned end on the release (rm_release) , the date gets captured in audit history and overdue sla breach time is updated right. Any pointers on why that is not captured and breach time not getting  updated ?

[Dr Atul G- LNG]

Hi @priyadharis 

Greetings!!

If you're referring to Release V2, let me clarify that R2 has been deprecated. There's no support available for it anymore, so it's best not to spend time on it. I recommend migrating your R2 to the new release product called DPR, which is a more enhanced version of Release V2 and is currently in active use.

[priyadharis]

We are not on V2

[Dr Atul G- LNG]

@Sai Teja1  @Bhanu29  can you help here.

[Bhanu29]

There is no planned end date field on the release task. The release task has a due date field, and updating this does not change the planned end date of the release. Could you please confirm if you are referring to the release task or the release phase? If it is the release phase, could you let us know how you are updating the planned end date of the release phase?

Please share some more details about the scenario, or alternatively, you can create a Case with the relevant details, and we will be happy to investigate the issue further.