Settings and activity
7 results found
-
126 votes
An error occurred while saving the comment 
jded
supported this idea
·
An error occurred while saving the comment jded
commented
URGENT: Technicians should be able to add time to a ticket without being able to see the rate of the contract or select the rate. This is important as right now there is no way for technicians to be able to log time without accessing all clients' contract rates, which are confidential.
-
24 votes
An error occurred while saving the comment jded
commented
I completely agree - there needs to be much more granular control of roles - they're currently not fit for purpose for an MSP. For example, we can't have a user with access to policy configuration, without making him a full admin and therefore providing him access to all the billing information. This is a security risk that needs a solution ASAP.
jded
supported this idea
·
-
12 votesjded
shared this idea
·
-
222 votes
Nice! The feature you requested is being considered for development. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
An error occurred while saving the comment jded
commented
This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.
jded
supported this idea
·
-
48 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
An error occurred while saving the comment jded
commented
This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.
jded
supported this idea
·
-
61 votes
An error occurred while saving the comment jded
commented
This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.
jded
supported this idea
·
-
126 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
An error occurred while saving the comment jded
commented
This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.
jded
supported this idea
·
An error occurred while saving the comment jded
commented
This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.
An error occurred while saving the comment jded
commented
This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.
An error occurred while saving the comment jded
commented
This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.
There needs to be much more granular control of roles - they're currently not fit for purpose for an MSP. For example, we can't have a user with access to policy configuration, without making him a full admin and therefore providing him access to all the billing information. This is a security risk for the business that needs a solution ASAP.