Darcy Vaughan
My feedback
4 results found
-
55 votesJT Abbott responded
Hey everyone, thanks for the continued support and votes for this idea!
We have increased the number of integrations we have and also have an integration with Zapier to help you connect with thousands of other services.
An open API is not currently in development, due to demand for other features and improvements. But please keep voting and sharing your comments!
An error occurred while saving the comment Darcy Vaughan supported this idea · -
99 votesCliff Mitchell responded
Thanks for your suggestion, Cameron! I love to hear user input on how we can improve ClockShark for you.
Let’s let folks vote on your idea so we can consider adding it in a future feature release. If you have any other ideas or suggestions, you can let me know at hello@clockshark.com :)
An error occurred while saving the comment Darcy Vaughan commentedA variation on this request. I would like employees to only be able to see the Schedule for a predetermined period of time which I set - i.e. - 2 weeks. Any modifications to the schedule which appear after this would NOT trigger notifications to employees and they could not see the schedule further out than 2 weeks (or whatever the predetermined time is).
Reasoning - We schedule things in advance and may tentatively assign an employee to the task. If it is several weeks in the future it is quite likely that it will be changed. Employees get cranky when they think other people are getting their work, but we need to begin working on schedules as early as possible. As vacation requests and new jobs come in, we need to adjust the schedule accordingly.
An error occurred while saving the comment Darcy Vaughan commentedI agree with this comment. I don't understand why the system requires you to immediately add an employee when I create a department. It seems like the system requires you to do things in an order that may not reflect how you do business.
The original comment seems to be the same issue but in a different part of the program.
-
33 votesCliff Mitchell responded
Thank you for sharing your idea, and allowing folks to have a forum to support and vote for it. We prioritize all suggestions with the most traction and support.
With great support, this idea will become one of our upcoming feature releases, so please keep voting.
An error occurred while saving the comment Darcy Vaughan commentedI agree with Lance and Shawn.
Without local time zones, it is my opinion that our company cannot use the software. It isn't reasonable to expect people to "interpret" the calendar or have various people switching the default time zone.
Most software with this problem stores everything in Greenwich Mean Time (GMT) and then uses the local time for display by either detecting it in the browser or picking it up from an employee setting.
Darcy Vaughan supported this idea · -
101 votesCliff Mitchell responded
Thank you for sharing your idea, and allowing folks to have a forum to support and vote for it. We prioritize all suggestions with the most traction and support.
Great suggestions spread like wildfire. With enthusiastic support, this idea will become one of our upcoming feature releases, so please keep voting. :)
An error occurred while saving the comment Darcy Vaughan commentedAlso could we change this from tool tracking to tool/equipment tracking to make it easier to find.
Thanks
An error occurred while saving the comment Darcy Vaughan commentedWe charge for some of our equipment and this may be on an hourly, half or day rate. Calculating our invoice we need to have separate line items for work performed and equipment used.
- surveyor 8 hours
- GPS 4 hours
- ATV 2 hours
- chainman 8 hoursDarcy Vaughan supported this idea ·
I think adding a standard Web Service API is the biggest addition ClockShark could make. When your software is integrated with other software within the organization it becomes very sticky within the organization.
Echoing another comment, we use a CRM system to create jobs. We would like to connect the creation of these jobs within CRM to the creation of a corresponding job in ClockShark for scheduling and execution.
On the other end of the process, we would like to take the hours worked and feed them into our accounting/invoicing system.
Until this feature (API) is available it is difficult for any larger company to use ClockShark.