No way for a privileged user to override a reserved name for a pillar/person

Bug #276488 reported by Tom Haddon
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Unassigned

Bug Description

Currently if you want to create a project with a reserved word in it's title (such as "launchpad") you have to create it with some other name and then run a manual query against the DB to update it. There should be an option for an admin to be able to override this and rename/create a project with a reserved name to avoid running manual queries against the database.

Related branches

Changed in launchpad:
status: New → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

This might be doable when we update the blacklist rules for private teams and projects.

Changed in launchpad-registry:
importance: Undecided → Wishlist
Tom Haddon (mthaddon)
tags: added: canonical-losa-lp
Revision history for this message
Tom Haddon (mthaddon) wrote :

Had to run a manual query again today for a project rename. I think we had said any SQL needing to be run is a problem, so perhaps we can bump up the priority of this bug? We tend to get a few requests a week of this type at least.

Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Low → High
milestone: none → 10.10
Revision history for this message
Curtis Hovey (sinzui) wrote :

This must be fixed in the private-project feature.

tags: added: pirvate-project
Ursula Junque (ursinha)
tags: added: private-project
removed: pirvate-project
Revision history for this message
Curtis Hovey (sinzui) wrote :

I think it is time to workout how to do this in the UI. We are blocked on field validation. We want admins and registry admins to have permission to name projects.

We commonly create alternate fields (with different validation rules) in views when we want to violate the behaviour of a field. I would like to solve this a different way. If this is just an web issue, then we could allow the view to remove the validation error after performing a secondary check that the user has permission. I do not think this is about the web UI, I might want to create several projects using Lp API. I want allow BlacklistableContentNameField to check if the user has permission to ignore the blacklist. Fields to not know about the user though. validation is separate from permission.

Curtis Hovey (sinzui)
tags: added: disclosure
removed: private-project
Curtis Hovey (sinzui)
Changed in launchpad-registry:
milestone: 10.10 → 10.11
Curtis Hovey (sinzui)
summary: - No way for an admin to override a reserved name for a project
+ No way for a privileged user to override a reserved name for a
+ pillar/person
Curtis Hovey (sinzui)
Changed in launchpad-registry:
milestone: 10.11 → 10.12
Curtis Hovey (sinzui)
Changed in launchpad-registry:
milestone: 10.12 → series-future
Revision history for this message
Curtis Hovey (sinzui) wrote :

There are some names that really cannot be overridden. There are some that
admins do need to change. There are other that commericial or registy
admins could be trusted to use. We need a way to define who can override
blacklisted name.

jml and sinzui discussed the issue and decided that the blacklist admin
views should permit admins to specify the team that can override the
namebacklist. When the team is None, the nameblacklist cannot be overridden.

Changed in launchpad:
assignee: nobody → Curtis Hovey (sinzui)
status: Triaged → In Progress
Curtis Hovey (sinzui)
Changed in launchpad:
milestone: none → 11.02
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui)
Changed in launchpad:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
tags: added: entitlement
Curtis Hovey (sinzui)
Changed in launchpad:
assignee: Curtis Hovey (sinzui) → nobody
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.