Forum

3.4.0 - Real work a...
 
Notifications
Clear all

3.4.0 - Real work allocation (Timers started post upgrade)

5 Posts
2 Users
0 Reactions
3,361 Views
(@rexeh)
Posts: 85
Active Member
Topic starter
 
[#1277]

Looks like any timers started post upgrade are causing real work allocation page to fail to load.

2013-07-22 15:56:10 ** ERROR ** ERROR **
2013-07-22 15:56:10
** ERROR ** on file '/var/www/vhosts/oria/oria/model/ImputationLine.php' at line (152)
2013-07-22 15:56:10
** ERROR ***** cause = Undefined property: Activity::$WorkElement

Tested against 2 x users using timers today, both page loads fail with an error has occured (log above)

Switch USER to a user who hasn't done timers today, and I can see their current week + previous weeks fine.


 
Posted : 22 Jul 2013 19H03
(@babynus)
Posts: 14952
Member Admin
 

Hi,

Strange to get such issue in V3.4.0 as there was no dev around this code and functions.
I will investigate.
Ticekt #1146 recorded


 
Posted : 22 Jul 2013 23H36
(@babynus)
Posts: 14952
Member Admin
 

Case to product is specific :
- Resource enter some real work on ticket
- Ticket must be linked to planning activity
- Resource who enters the real work is not assigned to the planning activity of the ticket.

Issue is fixed.
Will be deployed in V3.4.1
In /model/ImputationLine.php; replace lines 152, 153 with :

				if (isset($obj->WorkElement)) {
				  $ass->realWork=$obj->WorkElement->realWork;
				  $ass->leftWork=$obj->WorkElement->leftWork;
				}

 
Posted : 23 Jul 2013 17H00
(@rexeh)
Posts: 85
Active Member
Topic starter
 

Also confirmed that this has resolved the issue.

Would this be related to the attached image?

It appears that a small portion of the work table are getting idProject 0 associated to the entries... I have been unsuccessful in tracking down the origin yet. This then results as you will know in the reports showing resources/time/money against "0"


 
Posted : 23 Jul 2013 17H36
(@babynus)
Posts: 14952
Member Admin
 

No, it's not directly, even if the same lines may be concerned.
I recorded Ticket #1148 to solve this issue that will not show direct errors but could lead to errors in reports.


 
Posted : 23 Jul 2013 23H41
Share:

Scroll to Top