Hi @Tommaso2 

 There is the "Phase" field with ootb values (such as "Requirement gathering" and so on) and also there is the related list where new phases can be created from scratch: which is the relationship between that field and the related list?

Atul: Yes, the OOTB Phase attribute is available. If you want, you can create your own custom phase as well. For demos, I usually prefer to use the demo data and explain that we can create new phases when required.

- Tasks have to be created against the "Phase" field or the phases in the related list?

Atul:

Yes, each phase has tasks associated with it. For example, in the Requirement Gathering phase, tasks can include:

• Stakeholder meeting

• Agenda sign-off

All tasks should be linked to at most one phase of the release.

- In a release it is possible to associate projects, incidents and so on from the related lists, it is just for tracking purpose right? Can you please provide a real case scenario?

Atul:

Yes, to link the projects, you need to install the SPM (Strategic Portfolio Management) plugin. Once installed, the SPM component will be available for use in Release.

As I mentioned, the DPR process goes from Idea to Go Live.

Real case 

You’re done with Release 1 (R1) and now preparing for Release 2 (R2). Due to BAU activities, any incident that requires L3 support should be linked only with R2.

Ideally, you would create a change request and link the incident to the change. Alternatively, if you prefer, you can link the incident directly to the release or known errors as well.

https://www.servicenow.com/community/digital-product-release-forum/digital-product-release-using-ser...