Support forum for your suggestions, questions and to notify us of any issues you may encounter.
0
Under review

Small Typo in API Docs

Luis Garcia Bustos 4 years ago updated by Matthew O'Riordan (Founder) 4 years ago 1

Hi I have found a typo in the api documentation.

Created_at item attribute at the Sprint object: it's duplicated and one of them refers to the completed_at attribute.


Great API!, using it now with Jupyter and Pandas to explore team metrics.

0
Planned

created_at of Sprint sometimes is null using API

Josef Biehler 7 years ago updated by Matthew O'Riordan (Founder) 7 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

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

0
Under review

Invitation Email Not Sent

Bryan 5 years ago updated by Matthew O'Riordan (Founder) 5 years ago 1
I have sent and resent invitation emails to several of my coworkers but it doesn't appear to be happening.  Is there a schedule or something associated?
0
Declined

UI colors has to be changed

Jaya Kishore 8 years ago updated by Matthew O'Riordan (Founder) 8 years ago 1
Answer
As we've not had a response to our initial comment, we're closing this ticket. Please feel free to post your thoughts and we'll reopen this ticket.
0
Fixed

When entering 50/90 estimates the error message that appears when the 90 value is less than the 50 value is incorrect - it says the 90 value MUST be less than the 50 value when in fact the reverse is true.

Carl C 6 years ago updated by Matthew O'Riordan (Founder) 6 years ago 0

When I accidentally entered a value of 1 for the 90 estimate after entering 5 for the 50 estimate an error message appeared stating that the 90 value must be less than the 50 value. The wording of the message needs to be corrected to state that the 90 value must be greater than the 50 value.

Answer

Hi 


This issue is now fixed.


Thanks for pointing this out.  If you come across any other issues please shout.


Matt

0
Completed

As a user I would like to set "Points" for each story via a drop-down menu so that I don't need to memorize the fibonacci sequence.

Steve Shapiro 8 years ago updated by Maxime Schmitt 3 years ago 11
As a user I would like to set "Points" for each story via a drop-down menu so that I don't need to memorize the fibonacci sequence.
Answer
This feature is now live in production.  When you land on a field, if you either start typing or press the down arrow, the Fibonacci list will be shown (assuming you are using a strict numbering scheme).

Shout if this does not work as expected.
0
Declined

time estimation is not related to points

Pierre-Olivier Dybman 7 years ago updated by Matthew O'Riordan (Founder) 7 years ago 0

When considering a sprint, time and points are approximately related and the coefficient is the velocity. When considering several sprint, the relation between points and time is more accurate.

But if you take one user story in particular, it's not at all related. I would like to be able to have a pretty complex user story that doesn't take that much time, or (more common use case) the contrary : a user story that is not at all complex (points) but require a lot of time to be completed.

Answer

Unfortunately we don't want to introduce two systems for time tracking.  You are right, it is possible to have complex stories that are quick to fix, and vice versa, but for the purposes of this backlog, the points are more a representation of effort required and as such correlate to time.  If we introduced a new field, this would only complicate things further.

0
Under review

Ability to track hours or story points

thomas 5 years ago updated by Matthew O'Riordan (Founder) 5 years ago 1
In our team we are paid via how many tasks we finish. Is there a way to track the story points or hours used on each sprint task?
Each month we would like to export the number of story points that each team member has closed within that month. None closed tasks shall continue over to next month. We could also do this export at end of each sprint. 
0
Under review

snapshots not working! getting an error message

Alex Strang 7 years ago updated by Matthew O'Riordan (Founder) 7 years ago 0

Hi there, when I try to make a snapshot I get an error message. The snapshot isnt taken. Previously it was duplicating the whole backlog and giving it the name of my snapshot

Answer

Hi Alex


I am sorry to hear that.  We have not received any notifications of errors on our side which is odd.


Is the problem still happening?  If you can recreate it, please send us the URL to your backlog at support@easybacklog.com and we'll look into it.


Sorry for the inconvenience.


easyBacklog

0
Under review

It would be helpful to display both the sprint start date (which is displayed) and the sprint end date at the end of the sprint page (which currently is not displayed)

Tammy 5 years ago updated by Patrick Grant 4 years ago 2
Currently the sprint start date is displayed at the bottom of the page, but not the sprint end date.  The scrum master can determine the end date by adding the days in the sprint (which is also not displayed) to the sprint start date, or by looking at the following sprint start date.  But it would be really convenient to see both dates and the number of days at the bottom of the sprint page.