Red Hat Bugzilla – Bug 821582
Read-only project page should show "active" versions as being read-only, not active
Last modified: 2013-03-03 22:19:49 EST
Description of problem:
If the status of a project is changed from active to read-only, it should be re-categorised into read-only instead of active. But the current behaviour of the project being changed its status from active to read-only, is still tagged as active under active versions.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.login as admin/project maintainer
2.pick up an active project and click "Edit Project"
3.change status to read-only
the project is still tagged as active.
the project would be tagged as read-only instead of active
changing status to Obsolete works properly
Please re-test with latest code.
still reproducible in Zanata version 1.6.0-beta-2-SNAPSHOT (20120531-0020).
When the project itself was set to read-only,the version underneath should become read-only regardless its previous status
When this happens, does the user at least get a permission error when trying to save changes?
Nothing happens where users can successfully save changes without getting an error.
Sorry, I was thinking that this was about whether the translation editor showed up in read-only mode, but that was another bug entirely. This is about the list of versions shown on the project page.
oops, sorry for the confusion if my description is not clear enough
With current implementation, if a project is read-only, the "translate" link in each of the version regardless their status is changed to "Open" which reflect read-only mode. Is that sufficient enough to determine the action?
Implemented UI changes on versions when project status changed.
VERIFIED with 1.8.0-SNAPSHOT (20120809-0024)
Fix released in Zanata 2.0.