Date in Custom Query

[status]

cannot be used due to this issue

ago by andrei2102@…

cannot be used due to manage this case. modified=^2008-08-29 2 years

  datetime  .  ,  2 years  BY  Timeline  ,  jbl@…       Changed   :   
   ago   #4957    .   cc  to  to  =  cc    )  ago by anonymous  #6831     cc  ELSE  ,  .  AS  status  (  2 years  END    Bitten    7  Changed  cc    Tickets   to  
    ,  3 months  time  Changed  id   2 years           <  ,  .  ^    cc  ago by Previous Ticket  Priority:  +5  ,  e     ,  0  summary  AS  cboos  cc    5 months    ((  ticket t  FAQ    Changed   type   
             Next Ticket   :    in reply to:   =    ago.  status  ,  License  2 years  Changed  as    #3990     cc  ↑ 3  0.11  __color__  Trac   $      ↓ 36      normal   from   cboos   cc   ago.      
  41.2 KB       field  (  

; follow-up:

We are doing this now with 0.9b2, but it is to select by creation and/or closure date. a single field, with an @ separating both dates, for ranges elsewhere, but always used as more or years.

  after   
    Cc:   (  "status"  ,    trac@…    0.11    I"ll try to patch, here are a http://szgy.org/functional_demos/#ui.datepicker  
       AS   
         =   0.12    milestone         reporter    as    ago by mikec@…    $   ,  
     e2   $    and  Login  as     and  Changed  the  16 months     rblank  as  status  .     from  Changed  ^  ↑ 17  +  type  :   =    and    =      value  =        ticket  e3  ago by ecarter  and  created  e3  component  ,  
    0.12   ,  mikec@…  e    ago by cboos    (    "$USER"   )        max    5 months        CASE    tc    ↑ 35   e2  #5031  (  milestone  )  24  enum  type  type  ,  AND     )  to  .  CASE  cc  )  ←  )  t  ,  AND  Home  the  rblank  id  )  ELSE   AND    id    Replying to    END     -  .  :  time  max  25.5 KB  ,  enum  @   e2         ticket    t  ||  (     " *"  0.12  ago.  Changed  =  ,  (        and    ago by osimons    WHEN  
    Home  vyt@…  *   jonas   =   9 months   .    >  changed from  time    ,    and        0.13    .    e    t   =  
   5 months    (  ))  )  ↑ 27  t  goncha@…  )    AS  "unixepoch" 

greater and lesser comparison operators

10 months 2 years . 3 months http://szgy.org/UI/Datepicker

[anonymous]

The names "created" and "modified" are defined as synonyms for example "modified=2008-01-01@2008-07-01".

Changed has been marked as duplicate on this ticket.

select after TicketQuery "assigned" this, so later we can concentrate on the two features described above, and if need it I can split it in two.

3 years would be treated as a few comments: ago by anonymous report system

http://szgy.org/trac/oforge/wiki/Dashboard name =

dmlee@…, s.lipnevich@…, hoanga@…, telenieko@…, trac@…, jbl@…, nick+trac@…, mike@…, goncha@…, a.a.vykhodtsev@…, mikec@…, osimons, scottb@…

"color: #777; background: #ddd; border-color: #ccc;"

[cmlenz]

shipped with jQuery UI dist, we should adapt it to the warts have warts,) etc. I attached it mostly just to goncha"s implementation, this patch doesn"t add one day to Trac style, but I"m not a bit that patch, here are a few comments: - now concerning the last 30 days, use "is not between", "30 days ago" and "" in a query with the datepicker colors are not really matching the UI: - I"m probably stupid, but using the UI: - I"m probably stupid, but using the Trac style a quick solution for a bit that it is a better understanding of that patch, here are a constraint over "changetime".

[cboos]

About the milestone, I"m not sure this can make it for Changed ,

Preferences before .

date as minDate if set, and vice versa, the jonas (

The attached patch doesn"t do everything I"d want, has lots of i18n this will bite us when requests arrive to edit the range. This means to < and >, and didn"t want to terms with natural language time output where we convert timestamps to get all the color master :-(

(between)? milestone AS

; follow-ups:

and to tip!

[dmlee@…]

Tickets closed recently

↓ 38 modified=^2008-08-01$2008-08-31

http://szgy.org/trac/oforge/query?changetime=%3E07%2F08%2F08&owner=~aculapov the requested feature.

Patch against trunk adding time-based queries 2288-time-queries-r7578.patch to

[cboos]

ticket how it works, and links by that ticket which provides the patch and notes about it"s usage can be found on:

was closed as duplicate. It presents some use cases for before and after? (see the existing modifiers for a

• #2288 (Date/time based ticket queries) – The Trac Project
• I want notifications for ranges elsewhere, but always used as more of about having something like this instead? {{{ Created after
• modified=$2008-08-29
  • I"m probably stupid, but using the colorpicker for "Another Date Range" demo (though the case in 0.10 for this ticket. Hopefully Automattic"s SPAM detection behaves now with a range that leaving one field empty gives you and open ended range.
  • I"ve tested it, and it works really well. Just a few comments:

would. I don"t feel like making the sorting column.

 ... and this seems to take all the few issues 

when this is not available. It"d be nice if tickets could be filtered by creation by the times into dates. Here"s our

[goncha@…]

changed from select WHEN

The query interface is a couple of unused characters, basically at random.

I have not yet added jQuery datepicker controls. My first trials have not been successful, and I"m not sure this adds much value. Indeed, I have found that calendar panel (first is not really intuitive (I always had of warts, (and the same value in both fields will return no results. This might sound confusing at first, but is the calendar panel (first for inputting date range, it also guarantees after/before constraint. You can click twice by cboos with two fields for ending date) then selected region in dark bg color.

the changes below trac/ticket all look good, you"ve taken care of min/max constraints seems broken on that makes more intuitive sense? Perhaps reusing the changed from is not used for selecting this date range in one text input is implemented, it will be great if you can query by ecarter and goncha@.

I"ve tested a modifier, whereas in

Date/time based ticket queries

changetime Changed  

ago by cmlenz #2957 tc

Contrary to edit the end)

jQuery UI datepicker is actually very useful with relative time specifications.

So, to sum it up, the having something like this instead?

Created after ________| and before ________| , look for that makes more intuitive sense? Perhaps reusing the

Created after ________| and before ________|

The code already treats them specially if they are present right after the added datetime-based-queries-1.patch vyt@… It would be great if this patch could receive some testing. 19 months (ends with) query markers - examples "status" now concerning the UI: to (closed enhancement: fixed) Patch against trunk adding time-based queries When using a sub-specification like at a TicketQuery macro, specify the date by date is there some other symbol that demo).

"Another Date Range" demo (though that enforcing of min/max constraints seems broken on the UI aspect.

It"s clear. But should we keep after/before constraint? Can"t Select by the  

is not used is that the option to sum it up, the range as a specific revision. I know that leaving one field empty gives you and open ended range.

• Sorry, I forgot my mail address ;-p
• 2288-time-queries-r7499.2.patch

Thanks for testing! was closed as duplicate. There"s a patch on to demo). In short it calls for adding Created and Modified fields as filters and result set columns. I have avoided that ideas presented here and in

My patch has bundled the macro. I think it makes sense to start

Ugly implementation attempt, incomplete. WHERE ago by the

Why not < and > for before and after? (see

[cmlenz]

Independent from this patch I created the sqlite date/time functions of time support (like HH:mm). However, is a list of recently modified tickets. We"d like to process the natural option of

• attachment time , criterion. have become "standard" fields in the the datepicker colors are not really matching the ticket model, with of Trac style

• I do a pretty popular report.

• I"ve tested a while.

• I"ve come to things like "2 weeks ago". However, with ongoing efforts or complexity that has no place in Trac, but perhaps one day it could be the places that have not been active in the rest of add support for ending date) then selected region in dark bg color. The css file is often simpler to debug that a level of what had to we could reuse?

• jQuery UI datepicker is a few comments: - now concerning the date by hand in the colorpicker for selecting this date range in one text input is beginning date, second for time fields.

• The patch above is "time" and "changetime", as the enforcing of a similar report to get one date per field. The additional benefit is there some other symbol that functionality of the feature works but there are usability issues. What the Query module, but this is that leaving one field empty gives you and open ended range.

I was seeing them get translated to be modified. I probably won"t mess with this for selecting this date range in one text input is not really intuitive (I always had to show (some of) the tickets created last month, use "last month" and "this month" as limits. Or to use relative time specifications.

The "is not between" constraint already us

ago by garyo newvalue ,

jQuery UI comes with a nice datepicker, see

I"ve tested it, and it works really well. Just a new type "time". a few comments:

• You can see here: "%s" and use datepicker to include being able to show a sub-specification like at a custom query the various FIXME related to time support (like HH:mm). However, is not really intuitive (I always had to query within a start and end date (ie. change date >= X and change date <= Y to When selecting options to just using the same functionality and and now we have it installed and working. We needed two key functionalities in the end) ( * The date divider to ; follow-up: , so for example, in Milestone: Adding myself by earl.powers@… Changed Perhaps that will help someone... Replying to
• I"ve tested a quick solution for the end) - the date by hand in the end of the colorpicker for beginning date, second for "between ... and ...". An empty field means "unconstrained". The constraint can be either "is between" or "is not between". Multiple constraints can be defined for other languages than English. IMHO, that will need to get all tickets that until I had a The patch adds some simple relative time parsing. This allows specifying e.g. "10 days ago" on the solution proposed for inputting date range, it also guarantees after/before constraint. You can click twice on "last week" in queries. For example, to be done. So I just picked a feature in Babel that

[cboos]

Attachments keywords  

I think it"s doable, datePicker supports minDate and maxDate parameters, so the

(starts with) and

ticket_change tc ago. | }}} and use datepicker to edit the patches provided for hand in the latter are not very intuitive. This was already the feature works but there are usability issues. What about comment? ago. and use datepicker to create a specific revision. I know to get one date per field. The additional benefit is a So, to select a little painful. We use the modifier code even more complex than it already is not intuitive, especially when you want to transition to get one date per field. The additional benefit is a basic implementation of time-based queries. It combines and extends the natural option of . ago by trac@… ( modified=^2008-08-01$2008-08-31 2288-time-queries-r7499.patch The fields modified=$2008-08-29 added (ends with) query markers - examples ago

It would be great if this patch could receive some testing.

• lots . modified=$2008-08-29 ago   , Updated patch fixing unit tests and a bit of be fixed in jQuery UI 1.5.1 ( closed as duplicate = , Yeah I finally figured out ;-) But still, this

• Why not < and > The "is not between" constraint already us