Support forum for your suggestions, questions and to notify us of any issues you may encounter.
+4
Planned

Need total backlog

Tony BenBrahim 4 years ago • updated by Matthew O'Riordan (Founder) 4 years ago 1

Completed items are no longer backlog, so if the program is going to show only one number, it should be the size of the backlog (not including accepted items). 

As a workaound, I will need to delete accepted items to get a correct number for my backlog (some have hundreds of items, if I have to export to Excel and filter to get a total backlog, it is no longer an easy backlog :-)

Answer

Hi Tony


To be honest, I completely agree it should work like this.  At present this is not the way the system works, but it something we will implement soon.


Matt

+4
Under review

Dependencies between user stories

Michael Sternberg 4 years ago • updated by Matthew O'Riordan (Founder) 4 years ago 0

Sometimes functionality implemented by user story is too big to be implemented within a single sprint. In this case we would like to create two user stories and to mark a second one to be dependent on the first one. Using order of stories inside of theme partially solves this problem, but not completely. Sometimes we have story that is dependent on a couple of other stories, or dependent on story from another theme..

Answer

Hi Michael


Whilst we certainly appreciate that sometimes this occurs, we are not sure the added complexity of supporting linked stories would benefit most users most of the time.  Do you not think that simply using some naming structure would solve this rare requirement?

Matt

+4

Burndown needed for the active sprint

Simon Poole 4 years ago 0
It would be useful to have a live burndown/burnup chart for the active sprint.

Normally in Scrum, the burndown chart is updated daily and visible to the team during the course of the sprint.  It's used by the team and the scrum master so they can see if they are going off track.
+3
Planned

quick search in sprint view

Roger Stich 5 years ago • updated by Matthew O'Riordan (Founder) 5 years ago 0
Hi,

it would be cool if i could use a quick search in the sprint view.

The Task i want to achieve is that i have a Story which i know very exactly (ID and the Text of the Story also, even aceptance criterias i know) because i took that story from another sprint.
Then i switched to the new sprint and have an enormous list of storys to the right.
Know i have 2 ways to find my story:
1. i scroll through the list but its a very very long list.....
2. i switch to backlog view and then pick the story from there

if i have an quick search in the sprint view it would be way easier.

 

Answer

Hi Roger


We agree completely, we need a search for larger backlogs.  It is something we are working on.  I will drop you a line as soon as we have something you can use.


Thanks for the feedback, and we'll do our best to get something out there for you.


Matt

+3
Under review

Ability to split a story

Craig C 6 years ago • updated by Matthew O'Riordan (Founder) 6 years ago 1
As a product owner, I want to split a large story into several smaller stories so that the stories can fit better into the iterations
Answer
Hi Craig

Thanks for the feedback.

In order to see if we can help you, can you explain at what point you split stories.  And when you split stories, what happens to the story you have split, is it disregarded?  I have spoken with a few users who have this need, and they say the normally add a new story and simply reduce the scope of the existing epic.  Does this not work for you?  If not, please explain your process and let me see what we can do.

Matt
+3
Under review

Add notes/comments for a theme

Michael Terkowski 6 years ago • updated by Matthew O'Riordan (Founder) 6 years ago 2
As a product owner, I would like to add notes/comments to a theme, so that I could better communicate specific issues or background information that relates to a theme.

As a user, I want to be able to view any additional information that a theme may have, so that I could understand better the background and motivation for the theme.

Sometimes, a group of stories has one common information that we want to capture, or notes about its priorities or motivation.

Idea: The notes/comments field doesn't have to be visibile. It can easily be an icon that opens a pop up. It is not an information that is required for grooming the backlog, but probably only visible on request when the user needs it.
Answer
We can understand the value of this, but we are actually trying to simplify the interface at present, and we are concerned that adding more icons will in fact complicate things.  Let us have a think about how, and if, we can accomodate this feature.  We'll update this ticket when this feature along with the other GUI improvements are in the current sprint.
+3
Under review

It woudl be good to have a Release Version field

-7778 6 years ago • updated by Matthew O'Riordan (Founder) 5 years ago 10
It would be good to be able to assign a story to a release tag, which can be just a text field. For example, it can be used to plan release 1.1 vs 1.2 or core release vs customer specific one. The backlog could then be sorted using this field.
Answer
Hi there

We are a bit reluctant to add more fields to the interface as it's already pretty crowded as it is.  However, saying that, a few people have been asking about a separate priority field, which perhaps could have a dual purpose of release / priority, which you could then sort by.  Can you explain a little more about how you use this release field so I can understand the process?

Matt
+3
Started

performance getting slow

Michael Terkowski 5 years ago • updated by Matthew O'Riordan (Founder) 4 years ago 7
The performance of the app seems to deteriorate over time. When we first starting using easy-backlog in January, it was snappy and fast, and nowadays I'm getting lots of complaints from users in our teams that the tool is sluggy and slow, increasing resistance to using it.
Answer
Hi Roger, Michael and Torsten


We did a major deployment today, and we came across an error that was causing failed requests with Roger.  It turns out that his backlog was taking just under 6 seconds to render on the server, which is completely unacceptable.


Because of the urgency of this, we've devoted a fair amount of time today to finding a solution, and we've released some updates today that have brought that rendering time down to around 1.5s, so a 4x performance improvement.  Whilst this is good, this is not good enough, and we'll be working to improve that even further.


Obviously there is client-side rendering performance as well, and we'll be considering Torsten's suggestions here too, to ensure the performance remains snappy even when working with large backlogs.


Sorry for the problems, and hopefully we'll have it lightning fast again even for our heavier users.  I expect you'll notice the performance improvements already.


Thanks,

Matt

+3
Under review

Add background colour to themes

Martin Georgiev 6 years ago • updated by Matthew O'Riordan (Founder) 6 years ago 1
It will be handy if you set the bg color for a whole theme so you don't have to set the colour for individual stories 
Answer
Ok, will look into this.
Can you tell me though, would you want the colour selection to simply colour all the child stories, or would it actually colour the whole theme?  If it coloured the whole theme, would child stories still be able to have their own colours as well?  Do you think this will be work and be useful?
+3
Under review

I would like the ability to add tags to a story.

Bryan Oakley 6 years ago • updated by Matthew O'Riordan (Founder) 6 years ago 2
We might have several stories spread across multiple themes that have to do with "reporting" or "training" or "editing". I would like to categorize my stories using such tags.
Answer
Hi Bryan

Thanks for the feedback.

Unfortunately I am really not clear what you are after.  Are you saying you want a story to belog to more than one theme?  And how are tags used?

Matt