A migration package needs to be approved by another developer before it can be executed.
Hi,
Currently, with Pulse v6.2.1, the only way to prevent one developer from executing his migration package without being approved by someone else is to restrict the security access. In the Groups page, you can restrict the access to the execution of the package using the following two groups:
Expected solution
It would be great if we could add an 'Approved by" flag for each migration package. The author can't approve its own packages.
We probably need a new setting in Pulse (off by default) where, when turned on, a migration package can only be executed if it has been approved by someone else.
We probably need a new column to show the person who approved the package:
Cheers,
Vincent