There are a few queries I'm looking to do through the API, but I don't think I can.
The most important is: I'd like to find all the work a user marked done in a time window. This is problematic in a few ways.
First, I can search for tasks where date_done is in a given range, but this is about task completion, and I am more interested in assignment completion. I don't think I have an efficient way, at all, to find all the work where a person has marked their assignment done in a time window.
Next, I accept that I can only look for whole task closure, but then I want to look for assignment closure dates. Those aren't provided in the API. Assignments have done_on but not date_done.
This means my approximation of "tasks a given person marked done in time window is "tasks marked done in a time window where a given person was ever assigned work on it." That's not a great approximation.
(I see now that I am largely repeating myself form https://liquidplanner.zendesk.com/hc/en-us/community/posts/115006644647 but I think I have more detail here, so I won't go delete this all.)
The other query I'd like to get is "tasks on which a user logged time in a given time window." I realize I can get this through the timesheet API, but it means dealing with two different response formats, so having a direct query for this in the tree would be useful.
Here's what I'm up to:
I want to get a concise description of the ways in which our plans do not survive contact with the enemy. At the beginning of an iteration (sprint), I take a snapshot of all scheduled work. At the end, I produce a report, per-member, of how reality at the end of the iteration compares to the plan. This shows all the scheduled work, along with the amount of time logged, whether it has been completed (distinguishing between assignment or task completion), or repackaged. My next goal is to show all the work that *was not planned* but which was completed or worked on during the iteration. I can use the timesheet API to get tasks that got worked logged, but I think I'm mostly out of luck for tasks that were created and marked closed with no logged time. (This shouldn't happen, but does.)
Please sign in to leave a comment.