Bug 1342527 (bmo_livecoding1)

Add support for a "nobody" group that has no members, which is 'partner-confidential' on BMO for instance

NEW
Assigned to

Status

()

Bugzilla
Bugzilla-General
a year ago
a year ago

People

(Reporter: dylan, Assigned: dylanAtHome)

Tracking

(Blocks: 1 bug)

5.1.1
Bugzilla 6.0

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
STR:

Add a group ($new_group) to a $product where one or more bugs are have a group set on them
that is NA/NA in the product group configuration ($bad_group)

Adding the group will trigger a confirmation: "Do you want to remove bad_group from $product?". Confirming that will produce the error message:

Can't call method "name" on an undefined value 

Expected Results:

Removing the group is probably sensible as this situation is weird to begin with (and subject to another bug to be filed after this) so when adding $new_group, it is acceptable if $old_group is removed.

Actual Results:

An exception is thrown.
(Reporter)

Updated

a year ago
Blocks: 1299921
(Reporter)

Updated

a year ago
No longer blocks: 1299921
(Reporter)

Updated

a year ago
Assignee: nobody → dylan
(Reporter)

Updated

a year ago
Alias: bmo_livecoding1
(Reporter)

Updated

a year ago
Summary: Error: Can't call method "name" on an undefined value when adding a group to a product → Can't call method "name" on an undefined value when adding a group to a product
(Reporter)

Comment 1

a year ago
Created attachment 8843046 [details] [diff] [review]
bug-fix.patch

Not sure if this is the right solution, but it's what happened after an hour of looking at it.
(Reporter)

Updated

a year ago
Assignee: dylan → dylan
Component: General → Bugzilla-General
Product: bugzilla.mozilla.org → Bugzilla
QA Contact: default-qa
Summary: Can't call method "name" on an undefined value when adding a group to a product → Add support for a "nobody" group that has no members, which is 'partner-confidential' on BMO for instance
Target Milestone: --- → Bugzilla 6.0
Version: Production → 5.1.1
You need to log in before you can comment on or make changes to this bug.