195459 - chfield [Bug creation] limits other fields in "Bug changes" queries

Status: RESOLVED WORKSFORME

(Bugzilla :: Query/Bug List, defect)

Description

[Stephan Koledin]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1

Since a chfield value of [Bug Creation] is done as @specialchart and any other
chfield values are done as @wherepart, they end up being exclusive rather than
inclusive. I don't have a good solution in mind at the moment, especially after
looking at the code/queries, but it seems that the current situation is sub-optimal.

For example, attempting to query for bugs that have either been created or
status-changed in the past x days only shows bugs for which both elements are
true. It would be much better if all the fields were OR'd, including [Bug creation]

Are there any plans to improve/fix this, or are we just stuck with the situation
for the forseeable future?



Reproducible: Always

Steps to Reproduce:
1. go to query form
2. select chfield of [Bug creation] and anything else
3. enter a reasonable chfieldfrom
4. search
Actual Results:  
results were not ideal, showing only bugs that have been recently created

Expected Results:  
should have shown bugs for which either creation date *or* other change date
fits the date range.

Comment 1

[Max Kanat-Alexander]

I can confirm this on the bugzilla-tip installation on landfill today.

Behavior is this: If you select [Bug creation] and any other "where one or more
of the following changed" fields, then all of the bugs returned are *required*
to have been created in the last x days. All of the other fields are OR'ed.

This should probably either be fixed, or the UI should be changed, or there
should be some documentation.

-M

Comment 2

[Dave Miller [:justdave]]

CCing the people that last messed with this code.

Comment 3

[Gervase Markham [:gerv]]

Related to bug 231315?

Gerv

Comment 4

[Antonis Christofides]

Gerv: Nothing to do with bug 231315.

Original reporter was right, but this changed when bug 37749 was fixed.

Max K-A: I can't reproduce this on landfill. For example, I choose
chfieldfrom=2d, and select [Bug creation] and Assignee. It returns bugs which
either have been created or for which the assignee has changed in the last 2 days.

Comment 5

[Max Kanat-Alexander]

Ah, indeed. Anthony is correct. It looks like this actually works properly. It
must have been resolved when bug 37749 was resolved. -M

Comment 6

[Antonis Christofides]

<pedantic>
Do we actually mark WORKSFORME in such cases? It was actually fixed, although as
part of the fixing of another bug.
</pedantic>

Comment 7

[Max Kanat-Alexander]

That's why Matty suggested WORKSNOW on the developers list.

In this case, though, when the fix wasn't actually a part of this bug,
WORKSFORME is currently the correct resolution. That way, you can see how many
*actual* bugs were fixed just by doing a search for RESOLVED FIXED.

-M