Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
| Line 53: | Line 53: | ||
You can also ask for bugs that have changed in a particular date range, using '''changed_after''' and/or '''changed_before'''. If you do, you may additionally specify that a particular field has changed in that time using '''changed_field''', and if you do that, you may also set '''changed_field_to''' to specify the new value. If you don't specify a field, it tells you whether the last_change_time is in the range given. | You can also ask for bugs that have changed in a particular date range, using '''changed_after''' and/or '''changed_before'''. If you do, you may additionally specify that a particular field has changed in that time using '''changed_field''', and if you do that, you may also set '''changed_field_to''' to specify the new value. If you don't specify a field, it tells you whether the last_change_time is in the range given. | ||
Set "changed_field" to "creation_time" in order to look for bugs filed between certain dates. (It is not possible to do a search which looks for an exact creation time, using a single parameter.) | Set "changed_field" to "creation_time" in order to look for bugs filed between certain dates. (It is not possible to do a search which looks for an exact creation time, using a single parameter. If you want to search for an exact creation_time, use Boolean Charts.) | ||
E.g. changed_after=2008-03-31&changed_before=2009-10-31&changed_field=priority&changed_field_to=P1 | E.g. changed_after=2008-03-31&changed_before=2009-10-31&changed_field=priority&changed_field_to=P1 | ||