Bug-reporting guidelines are editable even when not tracking bugs in Launchpad
Bug #187871 reported by
Matthew Paul Thomas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
1. For a project you have the ability to administer, in the "Change details" page, uncheck "Bugs in this project are tracked in Launchpad" if it is not unchecked already.
2. Try to change the project's bug-reporting guidelines.
What happens: You can.
What should happen: The project has no bug-reporting guidelines, because it doesn't track bugs in Launchpad.
| description: | updated |
| Changed in malone: | |
| status: | New → Confirmed |
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| Changed in malone: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
I found bug reporting guidelines for a project not using Launchpad to be a useful way to say, in prose, that bugs should be reported in some other particular location.
For instance, the ubiquity project does not use Launchpad bug tracking itself. Because its primary existence is as an Ubuntu package, and the upstream project is mainly for the purposes of code hosting, we ask people to file bugs on the Ubuntu package instead. There's no way to say that directly in Launchpad, though, so I set the bug reporting guidelines to "Please use https:/
Therefore, if you remove this feature, please add a text entry box after "Bugs are tracked: ( ) Somewhere else", so that we can have a free-text description of the recommended alternative bug tracker even if Launchpad is not capable of representing it by means of the other radio buttons.