Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
In our installation of ProjeQtor, I am Admin, with Manager+ type access rights.
AFAIK this is the highest type of access in ProjeQtor.
And yet I am unable to delete some projects that were started by others.
(Actually we had allowed our entire staff to experiment with ProjeQtor, in a bid to let them familiarize themselves with the software. Now we are trying to clean up the junk data, and start afresh. However, we do not want to erase the user-related data and profiles.)
I tried to investigate, and found that the Manager+ type access can do the following:
- Read all projects
- Can create
- Update and delete his projects
(In the Access rights > Access modes menu, I selected the Manager+ type, and looked at the Description field.)
So, my doubts are:
1. Is there any access type that can delete projects started by all other users?
2. Or does ProjeQtor allow only the project owner to delete his own projects, so that accidents never happen?
Manager+ can create, update and delete any project (unless you chaged access rights definition).
But you cannot delete projects with real work.
This is basic and unavoidable rule : you cannot delete anything with real work
Thanks for the response.
But there are many occasions where we must have an option to delete a project that has some real work:
- The project was a dummy project, meant for practice only (as in our case)
- A project is abandoned, and we do not want to have in in our records
- Old projects become irrelevant, and they need to be removed from the database.
- Part of an organization is hived off, and we don't want those projects
- A team is laid off, and we don't want its past projects
Can we have a provision where we can delete such project data?
BTW it is fine if we have some workaround for safe deletion of the project. For example, a script or a step-by-step procedure that cleans up the data from the back-end database without breaking any logic.
The project was a dummy project, meant for practice only (as in our case)
Then you'd better use a sandbox instance, not production instance.
A project is abandoned, and we do not want to have in in our records
Then cancel project : but real work spent on cancelled project must be taken into account (not deleted)
Old projects become irrelevant, and they need to be removed from the database.
Just close them.
But stats on real work must take into account work spent on closed project (so no deletion possible)
Part of an organization is hived off, and we don't want those projects
Just close and/or move to another parent project
A team is laid off, and we don't want its past projects
But they worked ! So real work must be kept !
BTW it is fine if we have some workaround for safe deletion of the project. For example, a script or a step-by-step procedure that cleans up the data from the back-end database without breaking any logic.
Such script does not exist.