Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

Tickets list is emp...
 
Notifications
Clear all

Tickets list is empty when "Estimated work" column is displayed (4.0.1)

7 Posts
2 Users
0 Reactions
8,254 Views
(@lfrugere)
Posts: 39
Active Member
Topic starter
 
[#1463]

Hi Babynus,

We discovered an issue when displaying "Estimated work" column on a large list of "Ticket" (376) : list of tickets is empty and counter is not refreshed.
When we selected a project with fewer tickets (about 100), list is correct.

I cannot reproduce this issue on your demo portal because there is not enough tickets.

Can you reproduce it on you latest version ?

Thanks,

Lionel.


 
Posted : 14 Nov 2013 12H02
babynus
(@babynus)
Posts: 14954
Main Contributor Admin
 

Hi,

I could not reproduce on track will all current tickets (247).
But I could when trying to display all tickets, including closed (1193).
When limitinng to first 500, display is correct.

I guess issue is due to some items containing invalid data.
I continue to investigate.


 
Posted : 14 Nov 2013 12H52
babynus
(@babynus)
Posts: 14954
Main Contributor Admin
 

Hi,

I found the issue : it was due to 1 Ticket having two workelement items (this should not happen).
This is due to an old issue that is fixed for long, but there could remain double workelement.

To fix this, just execute this SQL query :

delete from `workelement`
where (refType, refId) in (select refType, refId from (select * from workelement w) ww group by refType, refId having count(*) > 1)
and plannedWork is null and realWork is null

Don't forget to prefix table names if necessary.

Another good advise : save your DB before executing this query 😉

Fix will be generalized in V4.1.0


 
Posted : 14 Nov 2013 13H27
(@lfrugere)
Posts: 39
Active Member
Topic starter
 

Hi Babynus,

I execute query and commit but I still have this issue.

Any other idea ?
Any way to activate a debug mode ?

Thanks in advance,

Lionel.


 
Posted : 14 Nov 2013 16H23
babynus
(@babynus)
Posts: 14954
Main Contributor Admin
 

Are you sure the query was correctly executed ?
For instance, table name could be different if you use a prefix : it lust be changed on 2 places.

To find out which ticket causes the issue,I filter on id :
- id worked
- id >=100 and id did not work

So iteratively I found the id of the ticket causing the issue.
The looked into workelement table for this item.


 
Posted : 14 Nov 2013 17H49
(@lfrugere)
Posts: 39
Active Member
Topic starter
 

Thanks Babynus,

This issue related to multiple work_elements on a same ticket.

Fixed with this query :

DELETE FROM `workelement`
WHERE (refType, refId) IN (SELECT refType, refId FROM (SELECT * FROM workelement w) ww GROUP BY refType, refId HAVING COUNT(*) > 1)
AND (plannedWork IS NULL or plannedWork = 0) and (realWork IS NULL or realWork = 0)


 
Posted : 14 Nov 2013 19H23
(@lfrugere)
Posts: 39
Active Member
Topic starter
 

This query save my life ... twice


 
Posted : 22 May 2014 20H17
Share:

Scroll to Top