wbTeamPro Feature Request & Bug Tracker - wbTeamPro
View Issue Details
0010675wbTeamPro[All Projects] Bugspublic2017-01-30 09:312015-01-25 00:00
StarNetwork 
webuddha 
normaltweaksometimes
Resolvedno change required 
v3.4.x rc 
v3.4.x rc 
0010675: Time tracking for tickets - assign to the right client
Hi,
if we starting time tracking record, from ticket view page, than change the client ID from options tab, it's continue the record of the time for the previews client, it's should do one of the both:
1. stop the timer
2. "restart" new timer and record it for the new client
3. "switch" the record of the entire timelog to the new client ID

Regards,
No tags attached.
Issue History
2015-01-09 10:24StarNetworkNew Issue
2015-01-09 10:24StarNetwork
2015-01-09 10:41maxsys
2015-01-10 16:46tsuri55
2015-02-04 15:25webuddhaAssigned To => webuddha
2015-02-04 15:25webuddhaStatusNew => Under Review
2015-02-04 16:00webuddhaNote Added: 0010209
2015-02-04 16:00webuddhaStatusUnder Review => Resolved
2015-02-04 16:00webuddhaApplied to Version => v3.4.x rc
2015-02-04 16:00webuddhaResolutionopen => no change required

Notes
(0010209)
webuddha   
2015-02-04 16:00   
This is being closed after confirming the correct operation is taking place. The following is the correct operation:

1) Ticket Created
2) Ticket Associated with Client
3) Timelog Started
4) Ticket Client association removed
- At this point the timelog will be disconnected from the client

5) Ticket Client association restored
- At this point the timelog will be reconnected with the Client

6) Ticket associated with Project
- At this point the timelog will take on the Client association (if any) of the project

7) Ticket Client association removed
- At this point the timelog will maintain the Client association as dictated by the Project

8) Ticket Project association removed
- At this point the timelog will have no client association

9) Ticket Client association restored
- At this point the timelog will be connected with the Ticket Client

** Note **
Because Tickets are not maintained by wbTeamPro, client associations are passively monitored and maintained during the wbTeamPro controller shutdown procedure. This means that a modified client to ticket relationship will not be identified until the wbTeamPro system is loaded in either the client or admin interface.