Settings and activity
108 results found
-
2 votes
George Harb supported this idea ·
-
341 votes
George Harb supported this idea ·
-
128 votes
George Harb supported this idea ·
-
53 votes
George Harb supported this idea ·
-
13 votes
George Harb supported this idea ·
-
17 votes
George Harb supported this idea ·
-
36 votes
George Harb supported this idea ·
-
1,026 votes
George Harb supported this idea ·
-
1,559 votes
George Harb supported this idea ·
-
309 votes
George Harb supported this idea ·
-
186 votes
An error occurred while saving the comment George Harb supported this idea ·
-
64 votes
George Harb shared this idea ·
-
28 votes
George Harb shared this idea ·
-
108 votes
George Harb supported this idea ·
-
10 votes
George Harb supported this idea ·
-
19 votes
George Harb supported this idea ·
-
74 votes
George Harb supported this idea ·
-
59 votes
George Harb supported this idea ·
-
378 votes
George Harb supported this idea ·
-
70 votes
George Harb supported this idea ·
Actually, this should be considered a defect repair more so than an enhancement request.
The issue is that there appears to be a one-to-one relationship between contacts and agents when it comes to tickets. Whenever an agent is changed on a ticket, that agent is then assigned to all other tickets for that contact. It really should be a one-to-many or a many-to-many relationship. Either that, or decouple the agent assignment from the contact when it comes to tickets.