Bug 1027490

Summary: Project creation "restrict access" feature too ambiguous.
Product: [Retired] Zanata Reporter: Damian Jansen <djansen>
Component: UsabilityAssignee: Luke Brooker <lbrooker>
Status: CLOSED UPSTREAM QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: low Docs Contact:
Priority: low    
Version: developmentCC: camunoz, 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:54:24 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: 1066796    
Bug Blocks:    

Description Damian Jansen 2013-11-06 23:13:20 UTC 
Description of problem:
"Would you like to restrict access to this project to certain User roles?"

"Restrict access" implies that no unauthorised user can access the project, ie. view the project at all.
As the feature only applies to translations, it should indicate this clearly somewhere, ideally in the question itself.

Version-Release number of selected component (if applicable):
3.x

How reproducible:


Steps to Reproduce:
1. Sign in, go to $server/zanata/project/create
2. View the lower options of project creation

http://zanata.org/help/projects/create-project/ indicates what this feature does, but certainly wasn't what was expected.
Comment 1 Damian Jansen 2014-02-20 01:47:23 UTC 
I think this is handled in bug 1066796
Comment 2 Zanata Migrator 2015-07-31 01:54:24 UTC 
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-579