Persistent ID for Work Logs in Timetracker

Implemented

Follow

New post

Kai Gutzeit

• February 15, 2017 10:33

Using Timetracker API to integrate with other systems we want to have persistent ID for every worklog in Timetracker. We would like to implement an Update Integration, if a Time Entry gets changed on TFSTimeTracker side. Therefore, we thought we could use the RowID Attribute, which should be unique for each Time Entry, but its unfortunately not.

Any option to have persistent ID for Work Logs would be helpful

3

• Official comment

  

  Permanently deleted user

  • April 18, 2017 14:36
  • Edited

  Hello,

  We have just released update to VSTS with this feature included. From now on, when you get data via API IDs of records are persistent. With grouping enabled we also put unique computed ID into grouped rows.

  --
  Maxim

  Comment actions Permalink
• 

  Permanently deleted user

  • April 18, 2017 14:36
  • Edited

  Hi Kai!

  We discussed this item internally and found out that this is really required feature to have in API. We planned to this for next releases, I think we can have it in 3 weeks available. I will keep this request updated.

   

  Maxim

  0

  Comment actions Permalink
• 

  Kai Gutzeit

  • March 02, 2017 11:10

  Hello Maxim,

  thank you for your reply. As you mentioned, it is the most important requirement, we actually have for the API. We would be happy if we can use this feature in the next release in 3 weeks. 

  0

  Comment actions Permalink

Please sign in to leave a comment.