Be consistent in using Bug.markAsDuplicate

Bug #589660 reported by Deryck Hodge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Deryck Hodge

Bug Description

The bugs code is not consistent in whether or not we use Bug.markAsDuplicate versus setting duplicateof directly. There are call sites and tests that use both markAsDuplicate and set duplicateof directly. The webservice further complicates this by having readonly_duplicateof.

There should be only one way to mark a bug a duplicate.

Related branches

Deryck Hodge (deryck)
description: updated
tags: added: tech-debt
Deryck Hodge (deryck)
Changed in malone:
milestone: none → 10.06
Deryck Hodge (deryck)
Changed in malone:
milestone: 10.07 → 10.08
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Changed in malone:
status: In Progress → Fix Committed
Revision history for this message
Deryck Hodge (deryck) wrote :

Marking this qa-ok since it's an internal code change and tests pass.

tags: added: qa-ok
removed: qa-needstesting
Changed in malone:
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.