Now, when the user deletes a superproject (a Project that has subproject(s)) that Project is deleted but all the subprojects are "disconnected" from its parent and now become just regular Project (change the hierarchy from sub to project).
This means that the URL for those subproject changes also and probably other things are changed also.
We need to find a good pattern to handle this in a better way, but our first step will be to alert the user that this will happen when they try to delete the superproject.
The flow should be:
- user tries to remove the superproject
- user is informed in a very well detailed way what will happen and how the subprojects will be affected
- user accepts it
- project is deleted
For this issue we need:
Ref: #3649
Now, when the user deletes a superproject (a
Projectthat has subproject(s)) that Project is deleted but all the subprojects are "disconnected" from its parent and now become just regular Project (change the hierarchy from sub to project).This means that the URL for those subproject changes also and probably other things are changed also.
We need to find a good pattern to handle this in a better way, but our first step will be to alert the user that this will happen when they try to delete the superproject.
The flow should be:
For this issue we need:
Ref: #3649