Getting Parent returns 404 when Parent existed

Officially Answered

Comments

4 comments

  • Avatar
    Oleksiy Shtefchuk

    any chances? Ideas?

    0
    Comment actions Permalink
  • Avatar
    Vanja Pletikosić

    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

    0
    Comment actions Permalink
  • Avatar
    Oleksiy Shtefchuk

    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.

    0
    Comment actions Permalink
  • Avatar
    Vanja Pletikosić

    Hello Oleksiy,

    You can force synchronization from your Timetracker Settings -> Reporting & API -> Schedule update now.

    However a one or two minute delay might still happen.

    Please let me know if there is anything further I could help you with regarding this.

    Best regards,
    Vanja

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk