Correctly update the activity table about flags when moving a bug to a new product

ASSIGNED
Assigned to

Status

()

Bugzilla
Creating/Changing Bugs
ASSIGNED
13 years ago
5 years ago

People

(Reporter: Frédéric Buclin, Assigned: dkl)

Tracking

Details

(Reporter)

Description

13 years ago
When moving a bug to a product where some flag types do not apply, the activity
table should correctly display which attachment looses which flags. Actually,
all removed flags are considered as a whole, independently of their attachment;
not very useful.
(Reporter)

Updated

13 years ago
Target Milestone: --- → Bugzilla 2.22
(Reporter)

Updated

11 years ago
Target Milestone: Bugzilla 2.22 → ---
(Assignee)

Comment 1

6 years ago
Taking this as it has caused me headache recently and would like to see this fixed.

dkl
Assignee: create-and-change → dkl
Status: NEW → ASSIGNED
Target Milestone: --- → Bugzilla 4.4
(Reporter)

Comment 2

5 years ago
We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Target Milestone: Bugzilla 4.4 → ---
You need to log in before you can comment on or make changes to this bug.