Extend TimeTrackerEntry by AreaPathID

Implemented

Follow

New post

Luca Mahler

• July 04, 2017 09:21

Currently the TimeTrackerEntry delivers the AreaPath as a string. We consume the extracted data to map to the actual area path which currently leads to problems if an area path's name has changed. Thus, it would help us if you could provide the actual AreaPathID instead of just the distilled string.

Is there a way for you to supplement the API accordingly?

0

• 

  Permanently deleted user

  • July 07, 2017 18:58

  Hi Luca!

  I understand your case and we are already working on the feature to provide you a possibility to add any field from TFS/VSTS to Times Explorer data first and to Export/API a bit later. Check this feature request: https://support.7pace.com/hc/en-us/community/posts/115017897043-Request-to-add-arbitrary-fields-in-Columns-list-of-Times-Explorer-

  Please let me know if you have some specific requirements or some more ideas.

  Maxim

  0

  Comment actions Permalink
• 

  Permanently deleted user

  • August 22, 2017 12:18

  Hi Luca, 

  We added possibility to select any field from TFS/VSTS in Times Explorer! API is coming with this possibility later.

  Please see our post about this here: https://www.7pace.com/blog/introducing-layouts-and-all-columns-from-vststfs-in-times-explorer/

  Maxim

  0

  Comment actions Permalink

Please sign in to leave a comment.