Bug 903926
Summary: | Project maintainer should be able to define and save validations rules per project/document | ||
---|---|---|---|
Product: | [Retired] Zanata | Reporter: | Alex Eng <aeng> |
Component: | Usability | Assignee: | Alex Eng <aeng> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ding-Yi Chen <dchen> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | development | CC: | sflaniga, zanata-bugs |
Target Milestone: | --- | ||
Target Release: | 2.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 2.2-SNAPSHOT (20130215-1232) | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-27 03:25:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 846314 |
Description
Alex Eng
2013-01-25 04:42:09 UTC
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 > maintainers? 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 https://github.com/zanata/zanata/commit/0dad4407b232eb39def859ebfa1ea11e1efb0fc0 https://github.com/zanata/zanata/commit/9958b3e95c2a54103901b7c80a10928df3929ced https://github.com/zanata/zanata/commit/a9a1105ad35a7b166783b1a49d63af3a7c54d1b8 https://github.com/zanata/zanata/commit/094bf70a2d864fff9467ab494a6cf63f9d50f202 https://github.com/zanata/zanata/commit/876adddb50d601433ab4cf7f204d027980027615 https://github.com/zanata/zanata/commit/8dc741c310dab15949b4453e40f2e3fc307cb901 https://github.com/zanata/zanata/commit/a5a67027461b7f8137fad0f6782fde99a8a15d6c https://github.com/zanata/zanata/commit/17d3bf06080bd441535cb8b0a7e35f09a881d2eb https://github.com/zanata/zanata/commit/e182d96a786dac579cf675eb91b1b0b6914dee87 https://github.com/zanata/zanata/commit/e72c3699db9b506fc8eb1f7e2170c632c3cac81c fix unit test and implement inheritance of validation rules when create new version https://github.com/zanata/zanata/commit/09c218b246a054d307626a29085b94291619f97d https://github.com/zanata/zanata/commit/1987a76264be65dee89213a9b32c4c95e3f57e06 VERIFIED with Zanata version 2.2-SNAPSHOT (20130215-1232) Closing VERIFIED bugs for Zanata versions <= 3.1. Closing VERIFIED bugs for Zanata versions <= 3.1. Closing VERIFIED bugs for Zanata versions <= 3.1. Closing VERIFIED bugs for Zanata versions <= 3.1. Closing VERIFIED bugs for Zanata versions <= 3.1. Closing VERIFIED bugs for Zanata versions <= 3.1. |