Launchpad itself

Bug and security contacts settable for project that doesn't use Launchpad for bug tracking

Bug #202022 reported by Matthew Paul Thomas on 2008-03-14

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	Fix Released	Low	Unassigned	Launchpad itself 10.07

Bug Description

1. At <https://staging.launchpad.net/projects/+new>, set up a new project.
2. On the new project page, click "Bugs".
3. Click "Change bug contact" or "Change security contact".

What happens: You can set the bug contact or security contact.
What should happen: These links and forms don't exist for the project, because it doesn't use Launchpad for bug tracking.

It may save time to fix this bug at the same time as bug 113825.

See original description

Tags:

Matthew Paul Thomas (mpt) on 2008-03-14

description:

updated

Diogo Matsubara (matsubara) on 2008-05-09

Changed in malone:
importance:	Undecided → Low
status:	New → Confirmed

Curtis Hovey (sinzui) on 2010-03-10

Changed in malone:
milestone:	none → 10.03

Curtis Hovey (sinzui) on 2010-03-24

Changed in malone:
milestone:	10.03 → 10.04

Curtis Hovey (sinzui) on 2010-03-24

Changed in malone:
assignee:	nobody → Curtis Hovey (sinzui)
assignee:	Curtis Hovey (sinzui) → Registry Team (launchpad-registry)

Curtis Hovey (sinzui) on 2010-04-30

Changed in malone:
milestone:	10.04 → 10.05

Revision history for this message

Deryck Hodge (deryck) wrote on 2010-05-07:

Curtis, I see you assigned this to your team and even moved it a milestone, but isn't this fixed already, i.e. a project that doesn't use Launchpad just gets the "Configure bug tracking" link now?

Revision history for this message

Curtis Hovey (sinzui) wrote on 2010-05-07:

I think this is an error. They *should* be setable because the upstream bug report uses them. If you team chooses to remove the upstream contact from the group, then I would agree that they should not be setable.

Revision history for this message

Curtis Hovey (sinzui) wrote on 2010-05-07:

I think I could be more clear about how I read that report. We will not know the Upstream contact for any Upstream package/project in Ubuntu's upstream bug report. If Ubuntu does not need to know who to contact about bugs or security issues, then this bug is fixed, but someone needs to remove the hundreds of contacts that we have collected.

I think users should be permitted to set this information when they can. It makes Launchpad acceptible to other upstreams because they know Lp is a reliable source of this information. I think Ubuntu also cares about this information since they requested it in the report.

Revision history for this message

Deryck Hodge (deryck) wrote on 2010-05-08:

I agree with your comments here, Curtis. I misread the request here, but I agree with you now that I understand. Thanks for helping me understand the original intent better.

Cheers,
deryck

Curtis Hovey (sinzui) on 2010-05-21

Changed in malone:
assignee:	Registry Team (launchpad-registry) → Curtis Hovey (sinzui)
status:	Triaged → In Progress

Curtis Hovey (sinzui) on 2010-05-31

Changed in malone:
milestone:	10.05 → 10.06

Curtis Hovey (sinzui) on 2010-06-05

Changed in malone:
status:	In Progress → Fix Committed

Curtis Hovey (sinzui) on 2010-06-08

tags:

added: qa-ok

Curtis Hovey (sinzui) on 2010-07-07

Changed in malone:
status:	Fix Committed → Fix Released

Curtis Hovey (sinzui) on 2017-05-15

Changed in launchpad:
assignee:	Curtis Hovey (sinzui) → nobody

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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