If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

cloning a bug with disabled tracking flags results in: (flagname) is not a valid parameter for the Bugzilla::Bug::create function

RESOLVED WORKSFORME

Status

()

bugzilla.mozilla.org
General
RESOLVED WORKSFORME
7 years ago
2 years ago

People

(Reporter: Ginn Chen, Unassigned)

Tracking

Production
x86
OpenSolaris

Details

(Reporter)

Description

7 years ago
Tried to clone Bug 571213, failed to submit the bug.
Filed a new bug with same information, it works fine.

Comment 1

2 years ago
cf_blocking_thunderbird32 is a bmo specific field, assigning to the bmo product.
Assignee: create-and-change → nobody
Status: NEW → UNCONFIRMED
Component: Creating/Changing Bugs → API
Ever confirmed: false
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
i suspect we need to skip disabled tracking flags fields when cloning bugs.
Component: API → Extensions: TrackingFlags
Summary: cf_blocking_thunderbird32 is not a valid parameter for the Bugzilla::Bug::create function. → cloning a bug with disabled tracking flags results in: (flagname) is not a valid parameter for the Bugzilla::Bug::create function
(In reply to Simon Green from comment #1)
> cf_blocking_thunderbird32 is a bmo specific field, assigning to the bmo
> product.

that's true, but at the time this bug was created they were standard bugzilla custom fields, so making this bug bmo-specific isn't correct.


anyhow i just noticed bug is 5 years old.
many many things have changed, and this works without issue for me now.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Component: Extensions: TrackingFlags → General
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.