Hello
I can confirm that I have seen exactly the same behavior. My quick
workaround was to create reports with SQL instead of the simple query
language. An SQL query delivers the expected results. Not being much of
a SQL person, it took a little while to work out how to use the
suggested left outer join.
For example, my custom field is "loc"
SELECT id AS ticket, status, priority, owner,
time AS created, changetime AS modified, resolution, summary,
c.value AS loc, keywords FROM ticket t
LEFT OUTER JOIN ticket_custom c ON
(t.id=c.ticket AND c.name='loc')
WHERE status IN ('new', 'assigned', 'reopened') AND
owner='alerts-internal' AND summary LIKE ('%reporting%')
ORDER BY time DESC, c.value, priority
A solution to the default query problem would be great.
best
Mark
On 02/19/2015 01:30 PM, Hoiniji Rosonye wrote:
Hi there,
I just started using version 0.8, but I'm finding that I get duplicate
report entries whenever I query against custom fields. It seems that
the output reports each value until it reaches the selected value.
For example:
TRACK.INI
difficulty = select
difficulty.label = Effort
difficulty.options = 1|2|3
difficulty.value = 2
REPORT Output
id summary difficulty type priority product
1 Photo for Mr Joe 1 defect critical P
1 Photo for Mr Joe 2 defect critical P
CUSTOM Query
query:?order=type
&
col=id
&
col=summary
&
col=type
&
col=priority
&
col=product
&
col=difficulty
&
desc=1
Am I doing something wrong? Or am I misunderstanding how to set up
trac.ini or the custom query?
Thanks,
H.
P.S. As a newbie, I accidentally posted this to the TRAC group too.
So, you may see my question there as well.
