Closed Bug 926118 Opened 11 years ago Closed 11 years ago

tracking flags are being cleared when making a change to a bug using the webservice api after tracking flag migration

Categories

(bugzilla.mozilla.org :: Extensions, defect)

Production
defect
Not set
major

Tracking

()

RESOLVED FIXED

People

(Reporter: dkl, Assigned: dkl)

References

Details

Attachments

(1 file)

https://bugzilla.mozilla.org/show_bug.cgi?id=637806
https://bugzilla.mozilla.org/show_bug.cgi?id=675297
https://bugzilla.mozilla.org/show_bug.cgi?id=751539

Seems to be same flags as well each time:
status-firefox16: affected → ---
status-firefox17: affected → ---
status-firefox18: affected → ---
status-firefox19: affected → ---

Looking at the code, bug_end_of_update only works on active flags and does not mess with inactive flags so I am not sure why this is happening yet.

dkl
tbplbot is using the following to call BzAPI to update the bug adding a comment:

https://hg.mozilla.org/webtools/tbpl/file/4b9bf20dad6a/php/submitBugzillaComment.php#l24

Will try this locally to see what is occurring. Could be an issue in how BzAPI is calling process_bug.cgi to update the bug directly.

dkl
Sigh, not just inactive flags it seems:

https://bugzilla.mozilla.org/show_bug.cgi?id=910435#c40
Summary: inactive tracking flags are being cleared when tpblbot adds a comment after tracking flag migration → tracking flags are being cleared when making a change to a bug using the webservice api after tracking flag migration
Committed a fix for this issue and will need to be pushed to prod as soon as possible.

Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.2
modified extensions/TrackingFlags/Extension.pm
Committed revision 9059. 

We will also need to look into a script to replace tracking flags removed in the time period after the migration by tbplbot when it added comments.

dkl
Assignee: nobody → dkl
We may be able to do it by hand if it is not too many. Here is what I see so far.

http://dkl.pastebin.mozilla.org/3247322

dkl
Depends on: 926183
this appears to have impacted more than just api-driven changes; see bug 914888 comment 9 and bug 495123 comment 45.
Attached patch 926118_1.patchSplinter Review
Attachment #816649 - Flags: review?(glob)
Comment on attachment 816649 [details] [diff] [review]
926118_1.patch

Review of attachment 816649 [details] [diff] [review]:
-----------------------------------------------------------------

r=glob

::: extensions/TrackingFlags/Extension.pm
@@ +491,5 @@
> +
> +    foreach my $flag (@$tracking_flags) {
> +        my $flag_name = $flag->name;
> +        if (defined $params->{$flag_name}
> +             || defined $params->{"defined_$flag_name"})

nit: there's no need to check for defined_, as trackingflags aren't multiselect.
Attachment #816649 - Flags: review?(glob) → review+
Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.2
modified extensions/TrackingFlags/Extension.pm
Committed revision 9063. 

dkl
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: Extensions: TrackingFlags → Extensions
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: