Settings and activity
26 results found
-
1 vote
Kajay Woods
shared this idea
·
-
34 votes
An error occurred while saving the comment Kajay Woods
shared this idea
·
-
14 votesKajay Woods
supported this idea
·
-
1 voteKajay Woods
shared this idea
·
-
1 voteKajay Woods
shared this idea
·
-
15 votesKajay Woods
supported this idea
·
-
9 votesKajay Woods
supported this idea
·
-
5 votesKajay Woods
supported this idea
·
-
13 votes
An error occurred while saving the comment Kajay Woods
commented
This would be a great implementation, especially if you have a device with no printed label, and need to check whether you already have the device monitored.
Kajay Woods
supported this idea
·
-
20 votesKajay Woods
shared this idea
·
-
15 votesKajay Woods
supported this idea
·
-
2 votesKajay Woods
supported this idea
·
-
12 votesKajay Woods
supported this idea
·
-
2,289 votesKajay Woods
supported this idea
·
-
1,755 votesKajay Woods
supported this idea
·
-
24 votesKajay Woods
supported this idea
·
-
4 votesKajay Woods
supported this idea
·
-
32 votes
An error occurred while saving the comment Kajay Woods
commented
I believe this should be the case regardless. Let's say a technician accidentally places Ticket information into the wrong ticket, there is no easy way of removing said information. And then, if the built in Copilot is used for said ticket, its going to output incorrect information.
Kajay Woods
supported this idea
·
-
64 votesKajay Woods
supported this idea
·
-
920 votesKajay Woods
supported this idea
·
The idea is to streamline updates for selected devices only, with confirmation steps and respect for existing patch approval policies. It’s about reducing manual work, not removing safeguards—risky systems can be excluded or require extra approval before updates.