thank you for the input. We will put this to the roadmap as well.
If I may suggest an alternative way of reporting that is already available today, you can set performance monitors to capture these data points on tickets and represent the ticket reports per device to validate the need.
New Feature / Application Request
Application: Checklist
Which module is it about if you require it on top of any existing module?
On Comodo One, another module
What would be the function/feature name if you need to refer it later?
“Checklist” or “Tasklist”
What is the new feature, please describe it as you want it to be implemented.
This would be an application that allows you to create daily, weekly, monthly and yearly tasks for clients.
For example this could be a set of tasks for Customer A
Daily
Check Backup
Check server connectivity for VoIP
Weekly
Check for Server Application updates and install
It would be good if notes / results could be recorded and logged for reporting as well.
An example and maybe a good starting place is https://sourceforge.net/projects/taskstodo/
What is the benefit?
Gives the MSP daily etc… routines to complete for their clients which can be logged.
This allows for the MSP to make sure all clients have the base tasks and checks done as well as any automated tasks and schedules.
Who is going to benefit?
The MSP and all their clients
Regarding the implementation of Password Manager Module, it was rescheduled to Q1 of 2018.
I`ll be creating a support ticket on your request for the creation of Scripts using languages with CMD / Batch, PowerShell, Python, VB Script and Java.
Same goes with your feature request regarding Application: Checklist.
We really appreciate all your input and in behalf of Comodo One, we thank you for continue choosing us.
New Feature / Application Request
Application: External Services
Which module is it about if you require it on top of any existing module?
On Comodo One, another module
What would be the function/feature name if you need to refer it later?
External Services
What is the new feature, please describe it as you want it to be implemented.
Simple web application that allows an admin to create a list of useful web links and set permissions to who has access to them.
A good example is Office 365 or a web hosting portal. The MSP can open this app, select the Office 365 button which opens a new tab of the Office 365 login page
What is the benefit?
MSP can keep a track of portals and provide access to the right people. For instance KashFlow or QuickBooks only links for accounts members only for billing of SD tickets & contracts.
Please provide your feedback on below mentioned points,
It would be good to create scripts in all the following languages: -
CMD / Batch
PowerShell
Python
VB Script
Java
1.We can run custom scripts using python script procedure.
Example, you can use single python script procedure to create,run and capture output of custom Vb script or Powershell script or CMD/Batch script in the endpoint. We have already published such scripts in forum. Also please share us your script requirements : )
New Feature / Application Request
Application: Checklist
Personally I’m not that good at Python (learning fast) and did not know you could do what you are saying, could you provide us a link to the resource you mention?
This could be a saving grace as I have hundreds of scripts over the years and lots on systems like Spiceworks, Autotask etc
Unfortunately this is no where near what I’m asking…
This is great if you have a server or network setup for instance as you can create the project and tasks (tickets) for each section allowing you to work and get the system implemented correctly, but I’m on about a “To Do List” / “Check List” of tasks you as an MSP do for your clients on a daily, weekly, monthly and yearly basis which might end up with you creating a ticket to solve an issue you have found during one of these tasks.
In a plain osTicket environment (not Comodo customised version called “ServiceDesk”) I did create something with the use of a KB and CRON to read the KB and create tickets based on the information in there for daily etc task. This is a little basic and sure Comodo can do better, the best example is a backup check / log for instance…
Customer A
– Daily
– – Server 1
– – System F
This might be a simple “Completed Successfully” checkbox to say you have done it with a comments field which allows notes to why it passed / failed etc. This then allows for future expansion to the reporting section of C1 to report on tasks successfully complete or not as the case maybe.
I would also love to be able to natively specify the script language to execute - i.e. Batch/VBScript/PowerShell. Windows sysadmins are especially reliant upon PowerShell for a number of daily tasks, not to mention that it is the defacto standard for Windows administration. I would love to get this as a primary selection for executing remote scripts on my systems instead of Python - or, have a way we could just import our scripts quickly and let Python do all the dirty work of processing/parsing the output…
I love the prospects of Comodo, but some areas (like the script section) is a little kludgy to use.
Personally I’m not that good at Python (learning fast) and did not know you could do what you are saying, could you provide us a link to the resource you mention?
This could be a saving grace as I have hundreds of scripts over the years and lots on systems like Spiceworks, Autotask etc
Unfortunately this is no where near what I’m asking…
This is great if you have a server or network setup for instance as you can create the project and tasks (tickets) for each section allowing you to work and get the system implemented correctly, but I’m on about a “To Do List” / “Check List” of tasks you as an MSP do for your clients on a daily, weekly, monthly and yearly basis which might end up with you creating a ticket to solve an issue you have found during one of these tasks.
In a plain osTicket environment (not Comodo customised version called “ServiceDesk”) I did create something with the use of a KB and CRON to read the KB and create tickets based on the information in there for daily etc task. This is a little basic and sure Comodo can do better, the best example is a backup check / log for instance…
Customer A
– Daily
– – Server 1
– – System F
This might be a simple “Completed Successfully” checkbox to say you have done it with a comments field which allows notes to why it passed / failed etc. This then allows for future expansion to the reporting section of C1 to report on tasks successfully complete or not as the case maybe.
My team also has an interest in this. I wasn’t able to find any clear response to Frederik in the post history. Any chance you can share some details on what you have planned for this and what kind of time frame you have scheduled for its release?
I appreciate the work done by the C-Team so far on the products.
I am unsure if this has been mentioned somewhere – too many posts to read. I suggest some of the following is considered to enable easier/clearer communication between partners and the C – Team. I have the found the things below helped my team a lot in the past when implemented by other software vendors.
‘Vote for features’
I have read quite a few times in the posts that feature x will be released in quarter y, and then it gets pushed back/pulled forward, based on the dev’s progress. It is probably difficult to gauge the community’s ‘priority list’ if only the posts are used as base. Implementing a system where the community may ‘request’ features and all members can then ‘vote’ for a feature will assist in getting a clearer view of the community’s priority list. Features are marked by the C-team as ‘Considered’, ‘ In progress’, ‘Declined’, ‘Released’ etc. This normally works in the following way:
Each member gets a limited amount of votes – say 50 in total
Each member can add a Max of 3 votes per feature and until the feature is marked as ‘complete’ or ‘declined’ the votes applied by a member is deducted from his/her available votes. For clarity – if I add +3 votes on feature ABC I will only have 47 votes left until the feature is released or declined.
In the above way
Members can participate in contributing to the feature priority list
Members can see what features are already listed and their status – preventing posts about features everywhere and even beter stopping lazy readers like me from going through countless posts
The C-Team gets the above benefits as well – ie. get an indication of feature priority from the community & not having to answer the same requests over and over again.
Roadmap
The ‘roadmap’ may flow from the above – ie perhaps give a planned feature list for the next 6 months- it should further stop a lot of posts about “can we get/when will we get” Perhaps if a ‘status’ like ‘Planned next x months’ is added we can simply filter the ‘Vote for features’ list on this status and have a roadmap.
Status of services
Nearly every cloud service vendor we work with have a status page available nowadays
My first call is to go to the status page when experiencing an issue and if I find that there are one I will not open/add another post about it, I will simply revisit the status page every 10 minutes for an update – this should cut down on the ‘noise’ on the forum. It is only when I do not find a problem status on the status page that I will raise a flag. As the community grows I am concerned that any issue may lead to lots of posts and it must become tiresome for the C-team to answer every one of these?
I hope some of the suggestions help streamline communication and further enhance the solution.