Tus comentarios

Hi Michael

We've just done a major revamp to the story and theme management interface, and I think we've addressed pretty much all of your comments now.
  • Story and theme menu actions are found under a single tools icon simplifying the interface and removing clutter.
  • You can collapse themes now.
  • The lines between the user story field have been removed
  • [Edit] is now almost invisible and comes alive on roll over
Shout if you have any further suggestions.

Thanks for the feedback.

Matt
Hi Michael

Good news, you can now filter stories by either being completed, or by being assigned to a sprint.  Take a look under the Filter menu in your backlog.

Shout if you run into any issues.  Hope that solves your problem.

Matt
Hi Michael

We have now implemented drag and drop for stories between themes.

You can however still click on the move icon on a story and it will allow you to move it to another theme.  

Thanks,
Matt
Hi Howie

I am not sure what you are after here.  Can you please explain what you are trying to do?

Matt
Hi Howie

Thanks for the suggestion, however I am not sure what you mean by add spikes.  What are you expecting when adding a spike?  How will it effect the interface, the data, the reporting?  If you could describe in some detail what exactly are you trying to achieve, then perhaps we can find a solution.

Matt
Hi Jason

Thanks for the feedback.

Please read a recent request in regards to bulk upload / import features at http://easybacklog.userecho.com/topic/96806-as-a-user-i-want-a-bulk-upload-facility-so-that-i-can-import-user-stories-from-a-spreadsheet/

It's actually surprisingly complex, and I'm just not sure it's going to end up saving you that much time as you'll spend as much time ensuring your Excel sheet fits a strict format as you would just entering the information into easyBacklog.  It would really help if you could explain why you cannot enter into easyBacklog at the outset, and what these other sources may look like?  

Matt
Hi Jason

Thanks for the feedback.  I'm not quite sure how you would envisage things working via email?  Would a story automatically be added if you emailed it in?  If so, how would you specify the fields such as what is a comment, what is an acceptance criteria, what theme to use etc?  Would be good if you explained in more depth what you were thinking.

Matt
Hi Gary

To be honest, you're the first person so far who has raised this as a problem.  I can appreciate how you work though, and not thinking about themes at the outset is certainly a reasonable request.  

Adding an add story button is a very quick fix, and we'll schedule that in.  Allowing a story to be added directly to a backlog and not a theme is a big change and would require significant work.  If a few more people ask for that then we'll definitely address it, but at this stage we have to put our focus on features that most people are asking for.  I hope you understand.

Thanks for the feedback, it's greatly appreciated.
Hi Gary

Whilst I can appreciate that you don't necessarily think in themes at first, the entire interface revolves around the fact that you associate stories with themes at the outset.  

Could you not just add a theme called General and file all stories under that, and later on move them into the themes you set up?

Also, as a work around solution on our side, if we added an Add story button that is visible when you first set up a backlog (right now that does not appear until a theme is created), would you be happy for that Add story button to simply set up a generic theme and add the first story into that?  Would that suffice?

Matt
Unfortunately we are not going to build an import feature any time soon as it is very complex.  We would either need to build a fixed template you need to use in Excel, but then that kind of negates the usefulness of it as you'd need to repurpose your backlog into a suitable format.  Or we would need to build an extremely flexible import system with lots of functionality to deal with exceptions and missing / bad data, and we only seem to find people need this type of functionality once.

We built easyBacklog so that it's as fast to use as Excel when managing your backlog.  Most of our users now use easyBacklog to build and maintain their backlogs and no longer rely on Excel.  We highly recommend you use that approach moving forwards.

I am sorry we can't help right now, but we've thought about this a lot, and we just don't think there's an easy solution.

BTW. We are opening up an API soon however, so you can add and maintain your backlogs programatically...