On 11/01/2013, at 9:44 PM, Richard Hipp wrote:
> The "status" field is coming from the ticket table and thus shows the latest
> status. To show the latest status at some point in the past, you need a (I
> think) to first add a "status" field to your "ticketchng" table definition.
> Then modi
On Fri, Jan 11, 2013 at 3:07 AM, Steve Landers wrote:
> I'm implementing a "Changed Tickets" report similar to that in Fossil's
> ticket system, the main difference is I want to show who made the change. I
> do this by joining ticket and ticketchg
>
How is the /timeline?y=t page is insufficient f
On Fri, Jan 11, 2013 at 8:37 AM, Richard Hipp wrote:
>
> The "status" field is coming from the ticket table and thus shows the
> latest status. To show the latest status at some point in the past, you
> need a (I think) to first add a "status" field to your "ticketchng" table
> definition. Then
On Fri, Jan 11, 2013 at 3:07 AM, Steve Landers wrote:
> I'm implementing a "Changed Tickets" report similar to that in Fossil's
> ticket system, the main difference is I want to show who made the change. I
> do this by joining ticket and ticketchg
>
> SELECT DISTINCT
> date(ticket.tkt_mtime),
I'm implementing a "Changed Tickets" report similar to that in Fossil's ticket
system, the main difference is I want to show who made the change. I do this by
joining ticket and ticketchg
SELECT DISTINCT
date(ticket.tkt_mtime),
substr(tkt_uuid,1,10) AS '#',
status,
login,
t
5 matches
Mail list logo