Hi!
I created Epic/Feature/UserStory workitems hierarchy first, then logged time to UserStory.
Immidiately after it I requested via API worklog and workItem (UserStory) and request succeed, but when I requested Parent of UserStory, I got 404
when I retried it in about 1min, I got correct result
Is it possible to avoid this delay/problem?
-
Hello Oleksiy,
Thank you for reaching out to us. There is a delay after items and fields are created in DevOps before they will become available in Timetracker Reporting and via our API, as stated in our documentation.
Could you please explain your use case to us? Why do you need to be able to see work items hierarchy in the Timetracker API immediately after they have been created? The delay is a short one of about 2 minutes, which is about the time it takes for a Reporting Refresh to occur.
Best regards,
Vanja -
Thanks for your answer.
We use 7pace API for synchronization - we store worklogs and workItems in our DB and try to synchronize it via backgroundworker each XX mins. In process of sycnhronization we also try to synchronize also workItem(Task) hierarchy - Task/UserStory/Feature/Epic. In reported case we are succeed at workLog/workItem level, but stopped at workItem Parent (Feature) synchronization step.
Please sign in to leave a comment.
Comments
4 comments