Multiple Projects <-> Change Association

You can now associate multiple projects as child entities with a change or associate a single project as its parent entity. For instance, let's assume a scenario where two or three projects are created because of a change. Ideally, all of them needs to be mapped for better tracking and management. With this feature, this is possible as you can now associate all these projects with the change as child entities. Similarly, for a project that was solely responsible for the creation of a change, it can be associated as a parent entity for the change. 

Who can perform Association/Dissociation? 

Users with edit permission for a change can only perform child/parent entity association or dissociation on that change. 

Users can only associate/dissociate projects that they have edit permission for. 
 

Associating project as parent entity with a change. 

When a project is responsible for the creation of a change, then it can be associated as the change's parent entity.


Associating multiple projects with a change
 

When multiple projects are created because of a change, you can associate those projects as child entities to that change from the Implementation stage of a change. 

To associate projects with a change,

 

 

A maximum of 25 project child entities can only be associated with a change.  
If a change that initiated multiple projects is deleted, then an option to cancel all the projects (child entities) will be shown before deletion of the change. Refer below image.

 


 

Notify Project owners on Association/ Dissociation

Project owners can be notified when changes are associated/ dissociated with their projects. They can also be notified if a change initiated by their project is closed/canceled/deleted. These actions can be done from under Admin >> Notification Rules >> Change

Use the various notification options as required. Use Customize template to modify the notification content.