Description of problem:
Bug #115499 does not have a 'changed' date. For an example see the
last entry in
This behavior is bad since I often search for bugs which were modified
in the last X days. The no-changed-date breakes this and returns nothing.
ok, adding some senseless text to set a 'changed' date... perhaps you
are using 'changedin' queries and have not seen this report therefore...
bug still alive and very annoying...
any news or a schedule when it will be fixed?
still no change...
http://bugzilla.redhat.com/bugzilla/buglist.cgi?changedin=1 works fine
for changes made to bugs in the last day.
For newly added bugs use
instead (new bugs from 2003-03-16 till now).
IIuc you want the "changed" flag also to be initialized on bug
creation, so the total of both results shows up in the first query.
Can this be configured in bugzilla, or does it need a code change? If
this is a configuration option I would vote to indeed initialize
"changed" on bug creation. Otherwise this becomes an low priority RFE.
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.