You're able to create new questions on Launchpad even when questions is not avilable to a project

Bug #1079678 reported by Laura Czajkowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
j.c.sackett

Bug Description

I've closed down questions on Launchpad for a project. People are still able to create a new question on there due t adding it via the URL, this leads to people asking questions and them not being monitored or replied to and frustration for the user.

Related branches

Changed in launchpad:
status: New → Triaged
importance: Undecided → High
tags: added: lp-answers ui
Curtis Hovey (sinzui)
tags: added: distributions projects
Deryck Hodge (deryck)
tags: added: private-projects
Revision history for this message
Richard Harding (rharding) wrote :

This isn't unique to private projects. It's a standard issue with the way questions work.

The +addquestion doesn't check if questions have been configured at all. I did a test on qa staging and can add a question without ever configuring it on the project.

Project level
https://answers.qastaging.launchpad.net/test-public-project

Added question
https://answers.qastaging.launchpad.net/test-public-project/+question/188579

Revision history for this message
Curtis Hovey (sinzui) wrote :

Yes, that is how Laura discovered the issue. +addquestion needs to check if the form can be rendered on initialize() or __init__

tags: removed: private-projects
Revision history for this message
Deryck Hodge (deryck) wrote :

I agree with Rick. This is not a bug that is specific to private projects. It's a bug that affects all of Launchpad. I also don't buy that there's any real risk of disclosure here, based on how transitions from private to public will happen and based on who the users of private projects will be. I have heard Curtis' concerns on IRC, though.

However, the semantics of the issue are not worth arguing. We all agree bug 1085102 is a real issue for private projects, and Rick believes fixing that will as a by-product prevent filing questions against private projects. However, this bug will still remain for public projects on Launchpad.

j.c.sackett (jcsackett)
Changed in launchpad:
assignee: nobody → j.c.sackett (jcsackett)
j.c.sackett (jcsackett)
Changed in launchpad:
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
j.c.sackett (jcsackett)
tags: added: qa-ok
removed: qa-needstesting
Steve Kowalik (stevenk)
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.