today i found out that sometimes easybacklog doesnt print all acceptance criteria. In these Case there where many criterias and there was just not enough room in that layout.
While i understand that you dont want to mess up your layout i think we need an solution for that. Because having many acceptance critrias for a userstory are nothing special in SCRUM. And printing is absolute critical, because the daily work has to be done at the Task Board with printet user story cards and then i need all criterias.
At least the absolute minimum is that i need a message or somekind of information that i have too many criterias to print the story.
(But this still doesnt solve the problem that i cant do anything about it)
Maybe if you print the userstory as many times as you need to print the criterias.
(e.g. criteria 1-5 at first card 6-8 at the second)
Hope you find an solution
I tried to get acces to your API via HTTP request but I cant authorize me.
More informations on the image below
The request look like this:
Host: api.easybacklog.com Accept: */* Authorization: Basic XXXXXXXXXXXXXXXXXXXXXXXXX
We apologise, but we recently migrated a database and forgot to update the references with the API web service, meaning unfortunately all of our monitoring continued to work but all requests were going to an old database.
This is issue is now resolved. Please post in here if this issue still persists.
Hi, i sugest that tipo of persona could be added by project and then associated in every story
But the list of personas automatically updates as you add in new personas, and then suggests existing personas. I am not quite sure I understand the problem.
Could you provide us the french canadian language (the same as french of France) with the devise in dollars ?
Sure, we'll get that done within a few weeks. Hope that is OK.
the user stories are broken in tasks. Why there is no column like a tasks list to give some proposal on how to complete the user story?
Customer support service by UserEcho