Toggl Time Tracking - Needed for Multiple Techs
We need a way to track time better.
Here is the problem.
The repair shopr built in timer does work hardly at all on a mobile phone browser.
Toggl works awesome but Repair Shopr only allows one Person.
So all this equals no good way to track time for onsite jobs.
So how are my techs supposed to keep track of Billable time when they are onsite? If they do this manually and say they can put it in later we will miss billable time which cost us money. Techs wont remember the exact time at each job and we will underbill.
We tried to share a Login.. But this doesn't work...
If you start the toggl timer on one Phone and you open the app on another phone it shows the 1st persons timer running. So when I have multiple techs on multiple jobs at the same time which happens every day what are we supposed to do?
When i seen the toggl integration i was like this is awesome and is the answer to the time tracking problem. But it comes up a little short without being able to have multiple techs,
So Please Vote to get Toggl integrated for Multiple Techs.
Planned means we want to do it, not that it’s scheduled for a dev to work on yet.
We just scheduled a few tasks that had 70+ votes, we can’t do this before those.
Patrick Moran commented
This is a fantastic integration but pointless if you can't use it on multiple members of your team!
Any update on this Troy?
Jimmy Fisher + Apollo Staff commented
Is this still "planned?"
Vince Mongiardo commented
My shop is just moving to RS from a ticket system built in-house, and I used the Toggl API stuff available on GitHub (https://github.com/toggl/toggl_api_docs) so that each of my tech's Toggle timers got pulled into the ticket system. You have to have the main/team Toggl API key and each tech's Toggl API key. It took some trial-and-error and the the functionality was basic (all that we needed), but if I can do it, surely the RS programmers can do it.
What needs to happen to get this implemented? Starting to lose faith in the RS team.
David Lawrence commented
omg yes please.
@Troy, we are up to 127 votes. I think its about time this moves passed “Planned” and into queue.
@Troy This has been planned for 2 years? I just ran into this road block when attempting to run a lab to bring our MSP division to RepairShopR. How am I suppose to bring in hundreds of seats and not allow dozens of techs track time? Seems like a foolish thing for a company wanting to be a PSA
I would like to see this as an option.
ILAN ELIYAHU commented
We integrated Toggl with RepairShopr so we can use Toggl to track techs tickets time more efficiently. It all works well when it's one user, the problem starts when i add techs to my team under Toggl website. Those newly added techs will not see the existing and new projects the main user can see and use for time tracking. In order for them to see a project i have to edit each project individually and give it an access to my team. That's of course not realistic to do!
@Troy, Please give us an update.
David Lawrence commented
wow - really? I can't believe this is a thing. Toggl integration only works for one person? :/ I don't even see the point in that. How can that be an integration for "1" tech ?
Can we get an update from an admin? "Planned" for almost 2 years doesn't seem very promising on that it will be added.
Is there a time frame for this feature? It shows Planned as of May 22, 2014.
We have a lot of repairs and onsite projects that have multiple techs working on them. Being able to use Toggl to track multiple techs' time would be extremely useful.
Michael Miller commented
It would be awesome if tech only saw the tickets assigned to them when they pulled up Toggl, instead of a giant huge list of all the tickets.
Further to this, the Toggl integration only has place for one API key, which I have put my Toggl API into.
This creates the project in Toggl (when it works) but that project is veiwable to me only so other techs can't see it to assign time to.
I have to go into Toggl and make the project viewable to everyone, which is a bit of pain since i have to do it for every single ticket logged!