7 commits

Author	SHA1	Message	Date
fr33domlover	50f12f855d	In ticket summary SQL query, group by ticket ID, not by discussion ID ... Each ticket has a single discussion ID, and each ticket has a unique one, so, given an inner join of tickets and discussions, I think there should be exactly 1 way select a (ticket, discussion) pair given any of these. But for some reason, PostgreSQL started complaining. Not sure what changed. Anyway, for now, I switched the groupBy from discussion.id to ticket.id, which is essentially the same, but for some reason makes PostgreSQL happy. It can't tell that given a discussion ID, there's exactly 1 way to choose the ticket. Or something like that. I wonder if I messed up something in DB migrations.	2019-04-18 19:35:04 +00:00
fr33domlover	e0de4cdcc7	Remove Discussion's nextMessage field, it's not being used anymore	2019-03-18 20:18:25 +00:00
fr33domlover	6088b1e117	Display tickets in list view the same as in tree view	2018-06-17 10:29:51 +00:00
fr33domlover	5909424644	Custom ticket field relevance filter by ticket status	2016-08-11 09:27:30 +00:00
fr33domlover	3329b49b2e	Turn boolean ticketDone into TicketStatus enum	2016-08-11 00:44:11 +00:00
fr33domlover	941bd0ea03	Ticket content edit form lets you edit custom ticket params	2016-08-10 18:52:26 +00:00
fr33domlover	dc54a89503	Ticket tree view page	2016-08-04 07:36:24 +00:00