-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Multi-User Workflow #1
Comments
@malizmaj @igryski @ethanclarke @cobuscoetsee I wanted to include you on this issue and provide a quick update. I was able to chip away at the web version this weekend and am getting close to a published release. There are some challenges associated with the multi-user transfer that I documented on the linked wiki page in the issue. @ethanclarke and @cobuscoetsee, how heavily do you utilize the Groups feature in Toggl? Are you primarily just assigning users to a project? I'm trying to figure out how to effectively test this so I don't cause a ruckus with your Clockify accounts. |
We're not using the groups feature. There aren't enough of us for that to be worthwhile. For our purposes, it would be fine to simply assign users on a project by project basis and leave it at that. |
Good to know. I think I’m going to skip groups for now and add them at a later date. All that’s left is time entries transfer and it’ll be good to go. |
Same comment here. We don't use groups either. Let me know if you need another tester. I have entries from both active and inactive users back to 2012. Thanks again for your hard work. |
Transfer works now accurately for all Toggl entries from multiple-users (we are 4 members), but it assigns them all to one user on Clockify workspace (the one whose API tokens were used in the interface). Any idea how to proceed with sorting these entries to correct users in Clockify workspace? |
@igryski So it looks like Clockify added the ability to add time entries for another user, but it's a premium feature: I think the way to get around this is to skip the time entry transfer step altogether if you're the one doing the setup. Here's the workflow I was putting together:
That's it for Multi User Mode, after that, each user accepts the invite, then goes to the tool and transfers their time entries using their Toggl and Clockify credentials. There's no need to worry about the projects/clients/tags being overwritten since they already exist. All I've done so far for the tool is add a step to select which transfer mode you want, but I haven't added the logic in to guide the workflow. This is all conjecture by the way, I haven't actually tested it to see if it will work. I can send you a script that will delete all your Clockify time entries if you want to try using this workflow instead. Have the members of your time try using the tool with their API credentials and let me know if it works. If you'd rather wait, I'm going to add a feature that allows you to delete your Clockify data to the tool itself in case something goes haywire. Also, FYI, be careful with pulling this repo down and running it locally, my intent is to host it on Netlify or Surge when it's ready. In the interim, I'm regularly making changes that could break it entirely or do some damage to your Clockify data. I'll be working on it today and over the weekend. My goal is to have the single user mode stuff wrapped up by Monday then move on to the multi user mode. |
Hey @mikerourke I found your repo while doing research for migrating from Toggl to Clockify. I'm interested in migrating my entire workspace with about 5 users over and I'd love to help out if you still need testers. So far, I've got the tool running locally, but the Multi-user option is crossed out. Can I help you test that somehow? My account at clockify is a blank slate, so I don't mind transferring and wiping it to start over. Thanks for your help and development on this tool! |
@anthonywkchan, I’m definitely planning on adding the multi-user workflow, but I’m currently in the middle of beta testing (sort of) the single user workflow. I’d like to ensure the basic functionality is working before moving onto the multi-user portion. I’m in the midst of a cross-country move right now, but once I get settled, I’m going to knock it out. I’ll keep you posted! |
Hi @mikerourke appreciate your hard work on this. Any update on how we can get 2 users entries and all the clients/projects into Clockify from toggl? If you have a workflow you need testing, I'm happy to take a stab at it :) |
@penguinmedia91 It's probably still going to take some time. It's a pretty massive undertaking and my availability is pretty limited right now (although I haven't forgotten about it!) I'll let you know when I have something to test. You could give this tool a try, it requires a little more configuration but it may work for you: https://github.com/pieye/toggl2clockify |
@mikerourke No problem :) I tried to get it running with the link provided but frankly, it was beyond my capabilities. I configured the python file correctly but I'm too stupid to get it to run on my Mac. Thank you for your continued hard work. |
Overview
Users need the ability to transfer entries for organizations/accounts with multiple users. I documented some of the challenges associated with this task on a wiki page.
The text was updated successfully, but these errors were encountered: