team visibility field changes the name, but I cannot see that

Bug #932192 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Steve Kowalik

Bug Description

There are two defects cause by recent changes to permit entitled users to create private teams.

1. Setting the visibility to private changes the team name, but since the visibility field was move from the third position to the last position, I cannot see that. The visibility really should be in the first or third position.

2. The visibility adds the private- prefix to the name, which is guarded by the blacklist. Only commerical admins can create a team with a name that starts with private-. The form errors and it is not obvious how to address the issue.
  * Stop adding the prefix when the visibility is set to private.
   It is rarely used. Team owners do not give a toss if their team name can be deduced.
  * Otherwise we need to fix bug 494801 which does not help the user create the team on the first submit
  * Extra credit, when visibility is set to private, set the subscription policy to restricted
   private teams must be restricted, but the form does not update so I get an error.
   This is an old issue, but I cannot find a bug about it

Related branches

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
Steve Kowalik (stevenk)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.