We mostly use "Import Times" feature to get the times into the system. Currently every time we run the import we have to manually map the columns.
If possible, please add a feature where we could automatically map the columns based on the headers in the first row of the pasted data. The recognized headers could be one of the following, matching columns in your system:
The duration header would simply be "Duration".
This feature could be optional and driven by an additional checkbox during the import: "First row has column headers" or something similar.
-
Official comment
Hey everyone. We have an open source NPM package for importing that could be adjusted by developers to provide the feature that you're looking for. Of course, this requires some development work from your side and isn't built-into the app, but it's a workaround. Would that work for you in the meantime?
Comment actions -
+1 ... I agree with Artur, this would be a very helpful addition. We recently migrated from Jira/Tempo and the 7pace interface is much clunkier for adding our time than Tempo was in Jira and therefor takes longer. The import is the only feature that allows me to come close to my previous amount of time it took me to add hours with Tempo (although it still takes longer with 7pace). As I have to enter hours on multiple separate projects every day I need to import multiple times. A simple match of the first line would save me from having to manually click and select each heading every single time I import.
-
Hi Stephanie,
thank-you for your message. My colleague Sascha reached out to you via email to ask if you'd be willing to catch up with us and discuss your experience with time-entry, we'd love to hear more about your use case!
Many thanks,
Andrea
Product Owner - www.7pace.com -
I too would love the ability to not have to select import headers every time. I use the import on several organizations per day, and having to do 12 precision clicks every time is not only slow, but it can get physically painful. I would love it if I could either include the headers in the copy/paste data, or just have 7pace remember the mapping after the first time.
-
I had already been looking at that package, thanks. I'll see if I can make mapping the organization name from a column in the import file an optional feature and submit a pull request when I get the time. Ideally, it would be best to have the feature built-in to the existing import, though.
-
Pull request submitted: https://github.com/7pace/timetracker-npm-import/pull/1
Please sign in to leave a comment.
Comments
9 comments