Bug 1034036

Summary: A project version can be marked active in an inactive project
Product: [Retired] Zanata Reporter: Damian Jansen <djansen>
Component: Component-UIAssignee: Alex Eng <aeng>
Status: CLOSED UPSTREAM QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: developmentCC: zanata-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-31 01:20: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:

Description Damian Jansen 2013-11-25 06:37:41 UTC 
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.
Comment 1 Damian Jansen 2014-08-06 01:03:23 UTC 
Tested at 3.5.0-SNAPSHOT (git-server-3.4.2-217-g2e4c78d) - still an issue
Comment 2 Zanata Migrator 2015-07-31 01:20:20 UTC 
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-438