Problem with the reports

[zineb BENAMEUR EL YOUBI]

Hello,
Recently, I made some modifications to my Trac , I added some new fields and delete some ones in trac.ini file.
In my section "tickets" where i can view the reports, there is a very big problem.
When i add the new fields to my SQL query, the old tickets (whitch were created before the modifications) disapeare from the query result.
Please, do you have any idea how i can resolve this problem?

Thanks,
Z. BEN

[Erik Bray]

You should post a sample of your query. It might be a problem with
your SQL. Tickets shouldn't just disappear from the results because
they don't have a value for a particular field.

[zineb]

Thank you for your answer, the query is correct I am sure because it works
for the new tickets ( created after fields addition)


Here is one of my queries:


SELECT component AS __group__, id AS ticket,
c1.value AS 'version', c7.value AS' charge totale passée en RI', c2.value
AS 'FOBs bloquantes', c3.value AS 'FOBs non bloquantes / majeures',c4.value
AS 'FOBs mineures',c5.value AS 'FOBs non OK suite aux tests'
FROM ticket t, ticket_custom c1, ticket_custom c2, ticket_custom c3,
ticket_custom c4 , ticket_custom c5, ticket_custom c7
WHERE (status = 'recette_terminee' OR status = 'retour_effectue' )
AND type = 'demande de validation'
AND t.id = c1.ticket AND c1.name = 'version_perso'
AND c1.ticket = c2.ticket AND c2.name = 'fob3'
AND c1.ticket = c3.ticket AND c3.name = 'fob4'
AND c1.ticket = c4.ticket AND c4.name = 'fob5'
AND c1.ticket = c5.ticket AND c5.name = 'fob6'
AND c1.ticket = c7.ticket AND c7.name = 'charge_tot'
ORDER BY component, c1.value

fob3, fob4, fob5, fob6 are new fields.
As a result, i only have few tickets ( 10) despite having more than 1200
tickets in the data base.

Thanks for you help,
Zineb

--
View this message in context: http://www.nabble.com/Problem-with-the-reports-tp23849771p23942377.html
Sent from the Trac Dev mailing list archive at Nabble.com.

[Erik Bray]

On Tue, Jun 9, 2009 at 9:01 AM, zineb<zineb.b...@gmail.com> wrote:
>
>
> Thank you for your answer, the query is correct I am sure because it works
> for the new tickets ( created after fields addition)
>
>
> Here is one of my queries:
>
>
> SELECT component AS __group__, id AS ticket,
>   c1.value AS 'version', c7.value AS' charge totale passée en RI', c2.value
> AS 'FOBs bloquantes', c3.value AS 'FOBs non bloquantes / majeures',c4.value
> AS 'FOBs mineures',c5.value AS 'FOBs non OK suite aux tests'
> FROM ticket t, ticket_custom c1, ticket_custom c2, ticket_custom c3,
>       ticket_custom c4 , ticket_custom c5, ticket_custom c7
> WHERE (status = 'recette_terminee' OR status = 'retour_effectue' )
>   AND type = 'demande de validation'
>   AND t.id = c1.ticket AND c1.name = 'version_perso'
>   AND c1.ticket = c2.ticket AND c2.name = 'fob3'
>   AND c1.ticket = c3.ticket AND c3.name = 'fob4'
>   AND c1.ticket = c4.ticket AND c4.name = 'fob5'
>   AND c1.ticket = c5.ticket  AND c5.name = 'fob6'
>  AND c1.ticket = c7.ticket  AND c7.name = 'charge_tot'
>  ORDER BY component, c1.value
>
> fob3, fob4, fob5, fob6 are new fields.
> As a result, i only have few tickets ( 10) despite having more than 1200
> tickets in the data base.
>
> Thanks for you help,
> Zineb

This is definitely wrong. But at any rate, this is the Trac
development mailing list. You should post this on the Trac users
list. [Hint: use the custom query interface to perform a query that
filters on your custom fields, and then check your Trac environment's
log to see the SQL that was generated]