
| Key: |
CHD-913
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Assignee: |
Unassigned
|
| Reporter: |
Joe Geck
|
| Votes: |
0
|
| Watchers: |
0
|
Clone this issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
| Value: |
2 - Significant Value
|
Summary:
Surrendering a ticket does not clear the "assign until" date, so the next worker to 'take' it inherits the "assign until" date.
Steps:
1) Click into a ticket and assign it to yourself with an "assign until" date via the 'Properties' tab, e.g.
Who should handle the next reply? = Worker A
Allow anybody to handle the next reply after = +2 hours
2) Click the 'Surrender' button up top
3) Sign out and then log in as another worker
4) Click into the same ticket as before, and click the 'Take' button up top
Result:
Observe the "assign until" timestamp is still set (in both the 'Properties' tab and at the top to the right of "Next Worker" in parentheses).
Note: If you surrender the ticket by simply using the 'Properties' tab like in step 1, i.e. choosing 'Anybody' to handle the next reply. The 'assign until' date will properly reset and this issue will not occur.
Also instead of taking the ticket in step 4 with the 'Take' button, you could theoretically use the 'Properties' tab and choose 'me' as the Next Worker. The timestamp will appear in the "assign until" field, but of course in this case you could manually delete the time before saving. Making it much harder to accidentally inherit the old date.
|
|
Fixed
Comment by Joe Geck [13/Nov/08 08:11 PM]
Verified fixed in dev build 797.
Any combination of taking and surrendering, no matter which way it's done (properites tab vs buttons), will properly clear the "assign until" field.
|
|