Hide Forgot
Description of problem: A version of a project can be ACTIVE, while the project itself is READONLY or OBSOLETE. This means the user can navigate to an invalid workspace, and a group holding the project will consider the stats of the version despite the project being obsolete. Version-Release number of selected component (if applicable): dev How reproducible: Easy always Steps to Reproduce: 1. Go to Projects, select / create a project 2. Create a version if one does not exist 3. Edit the Project, set the status to OBSOLETE, press Save 4. Go to the project version, change the status to ACTIVE, press Save 5. Upload a source document if one does not exist 6. Go to Groups, select / create a group 7. Go to Settings -> Projects, enter the project version and press Add 8. If no language is set, go to Settings -> Languages and add one Actual results: The number of hours to complete the group translations increases Expected: Group should not be seen in the stats. Though this is a bug for the ACTIVE status, not the group itself.
Tested at 3.5.0-SNAPSHOT (git-server-3.4.2-217-g2e4c78d) - still an issue
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-438