Klever

At the momment only global Managers and Experts and authors of last mark version can delete mark. Users can't remove first and last version of mark. So author of mark is always known. But if someone modified the mark, the mark can be completely changed, so it is the same operation as to remove mark and create new one. So auhtors shouldn't have an access to remove mark changed by manager for example.

Vladimir Gratinskiy wrote:

At the momment only global Managers and Experts and authors of last mark version can delete mark. Users can't remove first and last version of mark. So author of mark is always known. But if someone modified the mark, the mark can be completely changed, so it is the same operation as to remove mark and create new one. So auhtors shouldn't have an access to remove mark changed by manager for example.

Now this seems strange that an author of a last mark version can delete the mark. Indeed he/she can mistake and then remove other efforts. It looks to be better if just an author of all mark versions can delete the mark.

Besides, this likely will enable to remove a last mark version which is often useful.

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

At the momment only global Managers and Experts and authors of last mark version can delete mark. Users can't remove first and last version of mark. So author of mark is always known. But if someone modified the mark, the mark can be completely changed, so it is the same operation as to remove mark and create new one. So auhtors shouldn't have an access to remove mark changed by manager for example.

Now this seems strange that an author of a last mark version can delete the mark. Indeed he/she can mistake and then remove other efforts. It looks to be better if just an author of all mark versions can delete the mark.

If someone change the mark nobody can delete it? Cool.

Besides, this likely will enable to remove a last mark version which is often useful.

I'm not going to do it as users can select needed version and apply it.

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

At the momment only global Managers and Experts and authors of last mark version can delete mark. Users can't remove first and last version of mark. So author of mark is always known. But if someone modified the mark, the mark can be completely changed, so it is the same operation as to remove mark and create new one. So auhtors shouldn't have an access to remove mark changed by manager for example.

Now this seems strange that an author of a last mark version can delete the mark. Indeed he/she can mistake and then remove other efforts. It looks to be better if just an author of all mark versions can delete the mark.

If someone change the mark nobody can delete it? Cool.

1. If there are duplicates.
2. If they are too outdated and there likely won't be associated reports.
   Both cases are manager responsibilities.

Besides, this likely will enable to remove a last mark version which is often useful.

I'm not going to do it as users can select needed version and apply it.

In many cases it is just required to remove n last mark versions. It isn't convenient to restore some old version and then delete n last mark versions excluding a new one. Moreover in such cases there is always an extra version that corresponds to restoring.

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

At the momment only global Managers and Experts and authors of last mark version can delete mark. Users can't remove first and last version of mark. So author of mark is always known. But if someone modified the mark, the mark can be completely changed, so it is the same operation as to remove mark and create new one. So auhtors shouldn't have an access to remove mark changed by manager for example.

Now this seems strange that an author of a last mark version can delete the mark. Indeed he/she can mistake and then remove other efforts. It looks to be better if just an author of all mark versions can delete the mark.

If someone change the mark nobody can delete it? Cool.

Managers can delete everything. In other cases users need to resolve conflicts. Anyway, marks should be deleted just in two cases:

1. If there are duplicates.
2. If they are too outdated and there likely won't be associated reports.
   Both cases are manager responsibilities.

Fixed in "bradge-access".

Besides, this likely will enable to remove a last mark version which is often useful.

I'm not going to do it as users can select needed version and apply it.

In many cases it is just required to remove n last mark versions. It isn't convenient to restore some old version and then delete n last mark versions excluding a new one. Moreover in such cases there is always an extra version that corresponds to restoring.

Deleting last version is not just "clearing trash" (as it was supposed to be). It is changing the mark including connections recalulation. And user should be redirected to mark's associations changes page.

The problem still is not fixed. After the mark was changed the author of the mark can change it again and then remove all versions (except first and last) and then he can remove the mark as he is author of all versions again. I will allow to remove versions for its authors only (manager and global experts still will be able to clear all).