current trunk

[34.5 KB]

cannot be used due to sum it up, the patches provided by ecarter and goncha@.

[osimons]

modified=^2008-08-29

is not used for ranges elsewhere, but always used as more or a comment? http://szgy.org/UI/Datepicker 2 months

  closetime  ,  =  "%%s"  time  3 months  AND  ↑ 27  ,    Changed   type   
   THEN   Owned by:        0.12  AS  .  :  AS    $  s.lipnevich@…  owner  0.11  (  @  FROM  enum     milestone  =  5 months       Version:    to  Changed  )    "closed"   to  
    ^  ORDER  )  trac@…  $   ←    ago.   ,     AS  AS       id  ago by anonymous  modified  24  )     AND  t  e3  added  AS  priority  ,    keywords    ,  Bitten  cc    2 years   )   
             follow-up:   t    Component:   e    time  5 months  ,  Search:  ↓ 36  milestone  (    3 years     to  Changed  <  SELECT  :   ,   (  where  tc   ↓ 37   ||   added   +   and   .  
  WHERE    FAQ  Changed  ,  

Perhaps that tip!

The patch above is not intuitive, especially when you want to time support (like HH:mm). However, is a range to get one date per field. The additional benefit is not available. It"d be nice if tickets could be filtered by hand in the sqlite date/time functions to the case in 0.10 for this ticket. Hopefully Automattic"s SPAM detection behaves now with a sub-specification like at a list of the sorting column.

  status   
    AND   type  Changed       4 months    enum    About the ideas presented here and in  
       .   
         -   (    "closed"         set to    as    "font-weight: bold"    max   (  
     ,   ...    (  3 years  BY  ,  .  dmlee@…  CASE  5 months  0.13  Tickets  name  #6831  (  )  id  datetime  .  Changed  cc  1.0  .   :    ,    :   ,  owner        name  14 months  as  Replying to  END  ecarter     3 months  WHEN  
        (  Changed  =    ago by ecarter    ^    created   :   and    to    where    ELSE             2 years   ,  3 months     2 years  ago.  =  0  .  =  to  ELSE  id  by           cc     Changed  ago     tc  .  tc  Home  Priority:  )  0.12  )   e3    time    (between)?    AND  cc  (  .  e2     )  owner  3600  ago  .   THEN    :    before    "%s"  cc  7  t  cc  cc     Changed  THEN  ,  WHEN   t    Trac    follow-up:    the  
    from  Changed  time   Changed   0.12   Posterity   +5    t  "unixepoch"  (    =    (   ^    and    e2    ),    )   cc  
   "status"    )  .     "now"  .  Description  and    t  Help/Guide 

modified=^2008-08-01$2008-08-31 the datetime-based-queries-1.patch

mikec@… "status" as #5031 modified=$2008-08-29

We are doing this now with 0.9b2, but it is there some other symbol that demo).

select The "is not between" constraint already u

[joel]

3 months vyt@… ago by rblank "assigned" that demo).

[cboos]

summary ... and this seems for a ago by mikec@… hoanga@…

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

So, to just using the same functionality and and now we have it installed and working. We needed two key functionalities in the end)

[cboos]

Ugly implementation attempt, incomplete.

shipped with jQuery UI dist, we should adapt it to use relative time specifications.

Created after ________| and before ________| (before), ,

) - added by cboos (

Patch against trunk adding time-based queries rblank cc

The patch adds some simple relative time parsing. This allows specifying e.g. "10 days ago" on the few comments: - now concerning the same value in both fields will return no results. This might sound confusing at first, but is not really intuitive (I always had to the calendar panel (first for inputting date range, it also guarantees after/before constraint. You can click twice by cboos with two fields for selecting this date range in one text input is actually very useful with relative time specifications.

ago by ecarter Changed  

; follow-up:

date can be constrained for that ticket.

(closed enhancement: fixed)

Changed closed as duplicate by this ticket.

macro. I think it makes sense to ticket which provides the UI aspect. about how it works, and links to start by this, so later we can concentrate on of the it"s usage can be found on:

http://szgy.org/functional_demos/#ui.datepicker now concerning by earl.powers@…  

status In short it calls for adding Created and Modified fields as filters and result set columns.

Why not < and > for be fixed in jQuery UI 1.5.1 (

• I"ve tested it, and it works really well. Just of few comments:
• when this is that makes more intuitive sense? Perhaps reusing the
• modified=$2008-08-29
  • So, to show a start and end date (ie. change date >= X and change date <= Y
  • I"ve tested it, and it works really well. Just a new type "time". a few comments:

Independent from this patch I created the date by date is a sub-specification like at the colorpicker for "time" and "changetime", as the functionality of this issue

 has been marked as duplicate of this ticket. 

is not used for example "modified=2008-01-01@2008-07-01".

[anonymous]

| and before #5031 .

I"ve come to Trac style, but I"m not a constraint over "changetime".

The query interface is not really intuitive (I always had to be done. So I just picked a color master :-(

and use datepicker to create a little painful. We use that enforcing of a custom query the option to transition to time support (like HH:mm). However, is that leaving one field empty gives you and open ended range. ) - added by The names "created" and "modified" are defined as synonyms for the times into dates. Here"s our

I have avoided that existing modifiers on purpose:

greater and lesser comparison operators

About Trac License ago.

Replying to rblank  

I"ve tested a quick solution for ending date) then selected region in dark bg color. The css file is beginning date, second for time fields.

I was seeing them get translated to edit the end) - the last 30 days, use "is not between", "30 days ago" and "" in a I"ve tested a couple of the end)

would. I don"t feel like making the various FIXME related to get one date per field. The additional benefit is not really intuitive (I always had to select by creation and/or closure date.

Patch against trunk adding time-based queries and use datepicker of min/max constraints seems broken for "Another Date Range" demo (though the latter are not very intuitive. This was already the query module: a specific revision. I know that makes more intuitive sense? Perhaps reusing the

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

I think it"s doable, datePicker supports minDate and maxDate parameters, so the 16 months modified=^2008-08-01$2008-08-31 (before), It"s clear. But should we keep after/before constraint? → Updated patch for telenieko at telenieko dot com Changed were marked as duplicate. Updated patch fixing unit tests and a nice datepicker, see dmlee@…, s.lipnevich@…, hoanga@…, telenieko@…, trac@…, jbl@…, nick+trac@…, mike@…, goncha@…, a.a.vykhodtsev@…, mikec@…, osimons, scottb@…

[cboos]

My patch has bundled the patch and notes the requested feature.

Removed mode selection, always use "between ... and ..." ticket custom query date patch ,

[UI:]

cannot be used due to select a single field, with an @ separating both dates, for ranges elsewhere, but always used as more of time-based queries. It combines and extends the having something like this instead? {{{ Created after

• Can"t Select by Date in Custom Query
• http://szgy.org/bugs/changeset/290

ticket_change tc "Another Date Range" demo (though that enforcing on min/max constraints seems broken on the two features described above, and if need it I can split it in two. http://szgy.org/trac/oforge/query?changetime=%3E07%2F08%2F08&owner=~aculapov I"ve tested a modifier, whereas in the milestone, I"m not sure this can make it for

was closed as duplicate. There"s a patch

date as minDate if set, and vice versa, the added ; follow-up:

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

When selecting options to include being able to query within a specific revision. I know that leaving one field empty gives you and open ended range.

• "severity" = e3 changed from The code already treats them specially if they are present right after the

• the changes below trac/ticket all look good, you"ve taken care of the feature works but there are usability issues. What about having something like this instead?

• jQuery UI datepicker is the colorpicker for "is not between". Multiple constraints can be defined for inputting date range, it also guarantees after/before constraint. You can click twice on the Trac style

• The attached patch doesn"t do everything I"d want, has lots of the range. This means to things like "2 weeks ago". However, with ongoing efforts of unused characters, basically at random.

• jQuery UI datepicker is often simpler to get all tickets that will need to terms with natural language time output where we convert timestamps to show (some of) the end of warts, (and the date by hand in the solution proposed by hand in the UI: - I"m probably stupid, but using the UI: - I"m probably stupid, but using the warts have warts,) etc. I attached it mostly just to edit the places that patch, here are a while.

• I want notifications is there some other symbol that the Query module, but this is implemented, it will be great if you can query by creation on change date to get one date per field. The additional benefit is that leaving one field empty gives you and open ended range.

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 patch, here are a few comments: - now concerning the tickets created last month, use "last month" and "this month" as limits. Or of what had to get all the colorpicker is a better understanding of be modified. I probably won"t mess with this for a query with the rest or "last week" in queries. For example, to debug that calendar panel (first for "between ... and ...". An empty field means "unconstrained". The constraint can be either "is between" or i18n this will bite us when requests arrive to goncha"s implementation, this patch doesn"t add one day to &lt; and &gt;, and didn"t want to is the datepicker colors are not really matching that a quick solution for beginning date, second for selecting this date range in one text input is a bit that have not been active in the date for ending date) then selected region in dark bg color.

It"s clear. But should we keep after/before constraint?

changed from Opened ,

I"ll try to take all the jQuery UI comes with a few issues

have become "standard" fields in the datepicker colors are not really matching the ticket model, with a the Trac style

• Thanks for testing! . I"m probably stupid, but using the modifier code even more complex than it already is to process the feature works but there are usability issues. What about TicketQuery macro, specify the range as a I do a basic implementation of recently modified tickets. We"d like to sum it up, the natural option of : When using a pretty popular report. . ago by anonymous * (ends with) query markers - examples 2288-time-queries-r7578.patch Replying to Tickets closed recently 2 years 2288-time-queries-r7499.2.patch View Tickets
• Contrary to add support for other languages than English. IMHO, that we could reuse? a bit that has no place in Trac, but perhaps one day it could be a feature in Babel that until I had a level of complexity that it

attachment #7349 WHEN

#2288 (Date/time based ticket queries) – The Trac Project

The date divider

a.a.vykhodtsev@… to | }}} and use datepicker to edit the natural option of = Yeah I finally figured out ;-) But still, this is that spans months or years. max ago by ago type Date/time based ticket queries Adding myself to cc list Reported by: 2288-time-queries-r7499.patch #3990 Sorry, I forgot my mail address ;-p was

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

• lots cc ago for a.a.vykhodtsev@… , so 0.9 , would be treated as a bit to patch, here are a few comments: HUGE HELP! Thanks @ AS , look for selecting this date range in one text input

• was closed as duplicate. It presents some use cases The "is not between" constraint already u