Hi,
It is not possible to add constraint as "by another person".
The only way is to deal with profiles.
But it is easy to remove rights to the developer so that he can not change status.
Then you can define another profile, for instance "analyst", who will be able to change status.
But it is not possible to define cross constraints (one developer being able to validate work of another developer)

It will be nice to have constrain like that - just check if it not the same userID should not be very difficult...
It will be the same as you setting mandatory result field, etc.

The check is not difficult, you're right.
What is difficult is to set possibility to parameter it...
And define what you mean by "another person" : different from creator, different from responsible or different from the one who changed last status ?

Request is registered as ticket #701.

different from responsible

I understand request. Sure it would be nice to have that. But on the other hand Projectorria should remain handy and administatable.

Sometimes it is more better to trust the people, that they are knowing their job.

Try to explain that to TUEV people...

I see, we both on the same page with the same issues - auditing units and TUEV and ISO certifiction and PRINCE and ITIL and ... :silly:

Yes, if this will not be implemented, we probably will do it ourselves - by triggering the status change on the database side to restrict this kind of status change but it will be much better to have it in projectorria

Unfortunately this is clear requirement from TUEV certification board. Can it be set with some priority, please?

Hi,

Today this evolution is planned on V3.X (meaning current 2013).
I'll try to schedule it sooner if possible.

For information, I think that from TUEV point of view, the check in the history that the status has been changed by another person is enough. They is no contraint that the tool must force the rule, just be sure the rule has been applied.

Actually they asked for enforcement and we have it in current system. So, migration into projectorria should not be the step back...
Thank you very much!
Regards,
Evgueni

I think I have found simpler solution - I have added into 'Functions' new role - 'Reviewer'. So now it only question how to enforce that only reviewer can do the changes from review status...
Regards,
Evgueni

But this will not enforce that changes are made by resource other than responsible (if responsible is reviewer...)

Alos, if this fits your need, why not create a new Profile "reviewer".
Then you can define a workflow so that only "reviewer" can change a given status.

But again, this will not enforce that changes are made by resource other than responsible (if responsible is reviewer...)