Bug 1027490 - Project creation "restrict access" feature too ambiguous.
Project creation "restrict access" feature too ambiguous.
Product: Zanata
Classification: Community
Component: Usability (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Luke Brooker
Zanata-QA Mailling List
Depends On: 1066796
  Show dependency treegraph
Reported: 2013-11-06 18:13 EST by Damian Jansen
Modified: 2016-04-18 05:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-07-30 21:54:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Damian Jansen 2013-11-06 18:13:20 EST
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):

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-19 20:47:23 EST
I think this is handled in bug 1066796
Comment 2 Zanata Migrator 2015-07-30 21:54:24 EDT
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-579

Note You need to log in before you can comment on or make changes to this bug.