The "Changes made by users" feature in canned reports says some bugs are blocking themselves

RESOLVED WORKSFORME

Status

()

bugzilla.mozilla.org
General
--
minor
RESOLVED WORKSFORME
10 years ago
7 years ago

People

(Reporter: Frédéric Buclin, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

10 years ago
Look at the URL in the URL field: changes made by me on March 30 between 5:14am and 5:22am. You will see that it reports that 2 bugs are blocking themselves:

244204  2008-03-30 05:14:57 PDT  Blocks  244204

Same for another bug. What I did is that I marked them as depending on another bug, but it looks like this report mixed everything.

When viewing the history of these bugs, these entries do not appear, so this only affects canned reports.
(Reporter)

Comment 1

10 years ago
I think the reason is that both events (the bug marked as blocking, and the one marked as depending on the other one) have the exact same timestamp, and so they are mixed together. I suppose this means mass-changes must appear very badly in this case. One should try to see how data is being displayed when someone did a mass-change.
Rearranging this component to not have me as the default assignee, so that it doesn't appear like I'm intending to work on bugs that other people could be taking care of if they didn't think I was already doing them.  If this bug is a software issue on b.m.o and you'd like to fix it, the modified source is now available for the patching (see bug 373688).  Reassigning to the new default owner.
Assignee: justdave → nobody
QA Contact: reed → other-bmo-issues
Frederic: the URL you give doesn't work now; it says it needs a bug number. Can you clarify if this problem still exists?

Gerv
(Reporter)

Comment 4

7 years ago
This feature has not been ported to bmo 3.6 (it existed in bmo 3.4 only).
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

7 years ago
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.