Assigning checking rights via Project Plan

Question

When setting up a Project Plan, under Stages/Tasks you can assign whether any given Task requires editing rights. PT then assigns rights on the fly instead of through the old Users, Roles and Permissions tab.

However, it appears that the Checks may not do this. I just assigned “Missing Verses (XXX_Backtranslation)” and “Out of Date Verses (XXX_Backtranslation)” expecting the user to be granted permission to edit that back translation, but it didn’t work as expected.

Is this a bug?
Is it assumed that only project administrators will be doing the checks?

Answer 1

mnjames:

Is this a bug?

Most checks should give the needed permissions when they fail. If not, then it is a bug. However, BT checks really shouldn’t do anything (see below).

Iver+Larsen:

If so, there is a bug in that any person you assign these checks to are given editing rights in the main translation instead of in the back translation.

This is a bug. No permissions should be changed for back translation checks in either project because the Assignments and Progress can not change editing rights for another project (because of complications arising from having a project manage the permissions for another project).

Comments

The project plan for a vernacular project cannot control permissions to projects outside of itself, including the back translation project. As I remember, beta versions tried to allow this but it created too many problems and the access to back translation projects was limited. I will test this again later, but I think you have to manually give editing permission to anyone working on the Back translation project.

Answer 2

Are you referring to the checks that are also called back translation verse check and back translation status complete?

If so, there is a bug in that any person you assign these checks to are given editing rights in the main translation instead of in the back translation.

That is why I keep them unassigned and handle editing rights for the back translation through User Roles and Permissions.

Iver+Larsen