Get Started
Support Home

We’ve launched a new Help Center!

Visit the new Documentation space for Azure DevOps, monday.com, and Jira. Or, if you require any assistance or have any questions, please visit the new Customer Support Portal for Azure DevOps, monday.com and Jira.

Learn more

Time import - auto map column headers

Gathering Feedback
Follow
New post
Avatar
Artur Wawrzonkiewicz

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.

 

12

Comments

11 comments

Sort by Date Votes
  • Official comment
    Avatar
    Sascha Zierfuss

    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 Permalink
  • Avatar
    Maxim Shestakov

    Hi Artur!

    Thanks for your Feature Request.
    It is not in our current roadmap, so I've set state "Gathering Feedback" for it and let's see if the community will like this feature (we are setting priorities based on votes and activity on feature requests)

    Regards,
    Maxim

    0
    Comment actions Permalink
  • Avatar
    Stephanie

    +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.

    0
    Comment actions Permalink
  • Avatar
    Andrea Moro

    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

    0
    Comment actions Permalink
  • Avatar
    Jason Carter

    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.

    0
    Comment actions Permalink
  • Avatar
    Jason Carter

    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.

    0
    Comment actions Permalink
  • Avatar
    Morgan Gass

    I'm going to take a look at that API as well, but I would agree with Jason that it would fantastic if this could be something built in. Something as simple as having the ability to designate the first row of the data being imported as a header row would be a time saver.

    0
    Comment actions Permalink
  • Avatar
    Jason Carter

    Pull request submitted: https://github.com/7pace/timetracker-npm-import/pull/1

    1
    Comment actions Permalink
  • Avatar
    Maxim Shestakov

    Hi Jason!

    Our devs have merged your pull request. The npm package has been updated and can now be used. 

    Thank you for your input! 

    Maxim

    0
    Comment actions Permalink
  • Avatar
    Larry Smith

    Please add this functionality.

     

    The npm import is nice but not everybody is comfortable installing and using it. 

    This feature request is now 3 years old so I think it is about time to implement it in the UI :)

     

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Nicole Tropper

    Hi Larry, 

    thanks for reaching out! We get your point and the feature request sits in our backlog, but unfortunately the priority is not very high at the moment, so no ETA yet. We will keep you updated if anything changes. 

    All the best, Nici 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk