0
Planned

created_at of Sprint sometimes is null using API

Josef Biehler 8 years ago updated by Matthew O'Riordan (Founder) 8 years ago 2
Hello,
I am developing an application to import some of our Backlogs, Themes, etc into a Database for further reporting purposes.

But i'm running into troubles as the "created_at" attribute of some SprintStories contains "null" as you can see here:

{"created_at":null,"id":12083,"position":1,"sprint_id":3670,"sprint_story_status_id":4,"story_id":106162,"updated_at":"2012-06-26T14:07:43Z"},{"created_at":null,"id":11739,"position":4,"sprint_id":3670,"sprint_story_status_id":4,"story_id":59236,"updated_at":"2012-06-26T14:07:35Z"}

As the document does not state the attribute "created_at" to be nullable, I'm wondering whether this may be a bug?


Also there is a "bug" in the documentation of the Sprints (http://easybacklog.com/api#sprints).

In the list of available attributes on the left, you have listed "created_at" twice.

One of them should be named "completed_at" I think :)


Thanks for your help!


Best regards

Josef

Answer

Answer
Planned

Hi Josef


Thanks for pointing this out.  This is indeed very odd, as the business logic dictates that whenever a record is inserted into SprintStories, the create date should be set.  We'll need to look into what is causing this, apologies for the hassle.


We'll get the Sprint docs updated too, thanks for spotting that.


Matt

Answer
Planned

Hi Josef


Thanks for pointing this out.  This is indeed very odd, as the business logic dictates that whenever a record is inserted into SprintStories, the create date should be set.  We'll need to look into what is causing this, apologies for the hassle.


We'll get the Sprint docs updated too, thanks for spotting that.


Matt

Hello Matthew,


thanks!


Can you please tell me, whether the "UpdatedAt" Attribute is nullable or not?

Currently some (at least one) SprintStories have no updated_at value.


Have a nice weekend.

Josef, updated_at is technically nullable in our schema, but should never be nullable indicating we do have a bug somewhere in our system.  Apologies, but we will get this fixed.