Description of problem:
Project maintainer should be able to define and save validations rules per project/document
On 2013-01-29 10:19, Alex Eng wrote:
> Question regarding this RFE...
Well, it's your RFE! ;-)
> 1) Do we persist the validation rules on Project level OR Version
> level (new db table)? And I assume there will be a page for project
> maintainer to manage those rules against the project or version?
Both, inherited. Similar to custom locale lists.
> 2) The second part of the implementation is on persisting rules on
> document level (another db table). It will inherits the rules from
> project or version and apply to each of the documents.
> Who will manage the validation rules against the document? Do we need
> another similar page to manage the rules against each documents?
Where did the description "Project maintainer should be able to
define and save validations rules per project/document" come from? I'm not convinced it needs to be at the document level. At least to begin with.
> Currently all translators can on/off any of the validation rules, do
> we limit their access on turning on/off those rules set by
I think the general rules should be:
Project maintainer chooses soft (suggested/recommended) and hard (enforced) rules
Translators may disable suggested rules
Translators may not disable enforced rules.
Translators may enable extra rules.
Implemented required feature. See
fix unit test and implement inheritance of validation rules when create new version
VERIFIED with Zanata version 2.2-SNAPSHOT (20130215-1232)
Closing VERIFIED bugs for Zanata versions <= 3.1.