Settings and activity
107 results found
-
350 votes
George Harb
supported this idea
·
-
130 votesGeorge Harb
supported this idea
·
-
53 votesGeorge Harb
supported this idea
·
-
13 votesGeorge Harb
supported this idea
·
-
17 votesGeorge Harb
supported this idea
·
-
36 votesGeorge Harb
supported this idea
·
-
1,032 votesGeorge Harb
supported this idea
·
-
1,564 votesGeorge Harb
supported this idea
·
-
313 votes
Hi,
We wanted to let you know that your idea is currently under review by our product team. We are evaluating its alignment with our product roadmap and its potential benefits to our users.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
George Harb
supported this idea
·
-
188 votes
An error occurred while saving the comment George Harb
supported this idea
·
-
64 votesGeorge Harb
shared this idea
·
-
28 votesGeorge Harb
shared this idea
·
-
110 votesGeorge Harb
supported this idea
·
-
10 votesGeorge Harb
supported this idea
·
-
19 votesGeorge Harb
supported this idea
·
-
75 votesGeorge Harb
supported this idea
·
-
60 votesGeorge Harb
supported this idea
·
-
380 votesGeorge Harb
supported this idea
·
-
70 votesGeorge Harb
supported this idea
·
-
1,584 votes
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.