Uw opmerkingen

Hi Roger

On your first point about the open/collapse not remembering the stories that are filtered, that is a bug, and thanks for pointing that one out.  We've not noticed that one before, good spot. 

In terms of a default filter, we've thought about this and asked people, and we're not entirely sure we know what should be done.  If we have a default filter, it could get confusing for people who forget about this default filter.  The other option is to remember the last filter you set on the backlog you are using, and keep that setting when you return to it.  I think that would probably be the best option.  What do you think?

Matt
Thanks for the feedback, it's greatly appreciated.

We're doing our best to keep improving, so please do keep sending us feedback and we'll do what we can to accomodate.
Hi Roger

We've not added realtime updates in easyBacklog, however we do show you a warning at the bottom of the page when someone else is editing at the same time.  When we introduce our digital scrum board, we will be introducing realtime updates, so we'll hopefully resolve this issue then.  However, we do not plan on completely supporting real time updates in the near future as it can be very complex, for example:
  • If a story is deleted, should we replicate the delete?  This could be confusing for users seeing stories disappear.
  • What happens if two people are editing the same story simultaneously? 
  • If a story or theme is reordered, then the page will need to refresh to show the new ordering.  This can be quite confusing if you were looking at a backlog that keeps changing without your control.
I'll keep you updated when the new digital scrum board goes live as I think it will solve most of your problems as changes to stories and themes will be updated in realtime.

Matt
Hi Roger

Thanks for the feedback, clearly we need to address this if this as confusing.  In fact there is a "← Back to backlog" option in the top of the screen, however clearly that was not obvious enough.  We'll improve this.

Matt
Hi Robbie, sorry for the slow reply, I missed your response somehow.

I sort of understand about your requirement for JIRA, and it's certainly something we will consider.  I think you're right, I need to actually see how you use JIRA and your other tools to see if we can build something that is generic and will work for most of our customers.  I am always concerned about building something that is specific to one customer that in fact is a hinderance to most of our other customers, we have to carefully maintain that balance.

I am based in London, but I have just moved to France for 6 months, so I am based here for now.  However, I intend to pass through London at least once a month, so perhaps I could drop you a line when I am in London next and we could meet to run through all of this.  Alternatively, I could get one of my colleagues to pop over.  Where are you based?

BTW. In terms of import, I think you're right, if we at least provided a template that people could use for importing their backlogs, then that would be a good first step.  I'll push that up the list in our backlog.
Hi Alexey

We have now fixed this bug, and written some tests to ensure it does not return.

Thanks for pointing out.

Matt
Hi Roger

We have now fixed this bug, and written some tests to ensure it never returns, thanks for pointing it out.

Matt
Hi Taylor

I agree, the statuses you provided definitely seem more scrum like, and we've made that change.  

However, we would prefer not to make this configurable as this just adds another layer of complexity to the system.  We are trying to minimise the number of options people are presented with, so where possible we've taken a view on what is right and implemented the app accordingly.  However, if more people start to ask for this we'll be sure to reconsider.

Thanks for the suggestion.

Matt

Hi Michael

I suspect I know what the issue may be, but would like to confirm before we find a solution for this.  I think what is happening is that you are dragging a story into the sprint, and when you do that, you'll notice that the story you are dropping drops onto a grey box that appears.  When you drag it onto the right, and you do not drop onto a grey box, it will in fact not come out of the sprint.  It will only come out of the sprint when you ensure you move the mouse to a point where the grey boxes appear on the right.  I think it would make sense to move a story out of the sprint if dropped into a non-grey box area, but I wanted to first check that that is the problem you are experiencing first.

Can you confirm please?

Matt