| All Projects | wbTeamPro | wbTimeLog |
| Anonymous | Login | Signup for a new account | 2024-04-25 21:39 EST |  |
| Dashboard | Features | Bugs | Report Issue | My View | View Issues | Change Log | Roadmap | My Account |
wbTeamPro and wbTimeLog are actively being developed and supported.
We are working to update our tracker, changelogs, and documentation to convey this appropriately.
Thank you for your patience as we manage this period of growth.
We are working to update our tracker, changelogs, and documentation to convey this appropriately.
Thank you for your patience as we manage this period of growth.
| View Issue Details [ Jump to Notes ] [ 3 Votes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0010675 | wbTeamPro | [All Projects] Bugs | public | 2017-01-30 09:31 | 2015-01-25 00:00 | ||||
| Reporter | StarNetwork | ||||||||
| Assigned To | webuddha | ||||||||
| Priority | normal | Severity | tweak | Reproducibility | sometimes | ||||
| Status | Resolved | Resolution | no change required | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | v3.4.x rc | ||||||||
| Target Version | Applied to Version | v3.4.x rc | |||||||
| Summary | 0010675: Time tracking for tickets - assign to the right client | ||||||||
| Description | 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, | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0010209) webuddha (administrator) 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. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-01-09 10:24 | StarNetwork | New Issue | |
| 2015-01-09 10:24 | StarNetwork | ||
| 2015-01-09 10:41 | maxsys | ||
| 2015-01-10 16:46 | tsuri55 | ||
| 2015-02-04 15:25 | webuddha | Assigned To | => webuddha |
| 2015-02-04 15:25 | webuddha | Status | New => Under Review |
| 2015-02-04 16:00 | webuddha | Note Added: 0010209 | |
| 2015-02-04 16:00 | webuddha | Status | Under Review => Resolved |
| 2015-02-04 16:00 | webuddha | Applied to Version | => v3.4.x rc |
| 2015-02-04 16:00 | webuddha | Resolution | open => no change required |
|
Issue History |
| Dashboard | Features | Bugs | Report Issue | My View | View Issues | Change Log | Roadmap | My Account |
| Copyright © 2000 - 2024 MantisBT Team |
 |