Release Management Schedule

[Sam Ogden]

Hi All,

We are looking to move our release management processes into service now.   I am trying to get to grips with how the system works OOTB so we know what work we need to complete to fit our needs.

On the release record there is a Schedule section.   When creating a new record all the fields apart from the 'planned end date' are editable:

Does anyone know how the planned end date works? I would have thought it should calculate from the planned duration field but nothing seems to happen?

Also if you add a task to the release these fields all grey out with the message "Record has children so this field is calculated from child values".   Again nothing actually seems to happen.   None of the fields seem to complete with any information from the child task:

Release:

Child Task:

I've tried to look through the release management documentation and can't find anything around how these fields are meant to work.

Any help around this will be greatly appreciated.

Thanks

Sam

[Sam Ogden]

I'm struggling to find any information on how the above is meant to work.

I'm wondering if it is easier to remove these fields and have our own custom planned start and end fields which are editable - any thoughts to this will also be helpful

Thanks

[kristenankeny]

Were you able to find any information on this? We're also looking at release and this has confused me as well.

[Sam Ogden]

Hi Kristen,

I raised a hi ticket on this.   We are on Helsinki patch 11 and Hi were able to re-create the issue as well.   On Istanbul forward this seems to work as you would expect with the planned end date getting set depending on the planned duration and the planned start date.

Seems to be an error in Helsinki, but there was no existing PRB log for this.   As Helsinki is heading towards becoming unsupported when Kingston gets released there advice on this was to upgrade to Istanbul or newer.

Hope this helps

Sam

[kristenankeny]

Thanks - I'm seeing an issue where the planned start is locked on all records that i'm opening, even when there are no children. this seems odd to me. Even after creation, I would expect to be able to change the planned start for a record. Perhaps I'm misunderstanding their expected use case.