Ваші коментарі

Sure, I'll change this to reviewing as we will consider this option.
Hi Sanford


See http://easybacklog.userecho.com/topic/94379-drag-and-drop-ranking-of-backlog-independent-of-themes-eg-t1s1-t2s2-etc/ 

This is a feature we are considering, but is not something we have a solution for at present.  I appreciate it's a necessary feature, so we will introduce it at some point in the near future, and we have some nice ideas around how that can also be used to plan your sprints and see which stories would by default fall into which sprints.

When this is added, we'll drop you a line.

Sorry we can't be of more help right now.


Matt

This feature was introduced 4 months ago.
Yup, unfortunately shift-enter and shift-tab can be used for navigation as well.


We recommend you use ctrl-enter or alt-enter to insert line breaks which works in criteria or comment fields. 

Hi Sanford

Unfortunately at the moment we don't support the idea of custom fields.  It is something we've been asked for before, but most people unfortunately have not requested this feature as they've managed to use the fields available.  One of the things people often do is enter their custom fields as the first line of the comments field, or some other coding system like that.  Perhaps as an interim solution this would work?

The problem we have with introducing new fields is that it would impact the entire interface.  Where would the new field go without disrupting everything?  My feeling tells me it would have to go beneath the story (As a, I want to, So I can) fields.  However, if we added a new column all other fields would suffer in what is already a crowded space.  What do you think?

Matt
Hi Sanford


I am not sure I understand what you mean by "track by another metric".  Can you explain a bit more and I will see if I can help?

Matt

Hi Howie

In order for easyBacklog to know how to deal with sprints starting and ending, we have had to impose a restriction ensuring sprints never overlap.  However, if you need to start a sprint sooner, you can simply set the duration of the previous sprint to something shorter.  Would that work for you?

Matt
Hi Jaya

Thanks for the feedback, but it would be goo d to understand what specific thing needs addressing. We're on version 2 of our interface, and have another big UI review in the pipeline, but understanding a bit more about your input would be appreciated.
Thanks for the feedback Gavin. With each suggestion for a feature we need I consider the positive impact of adding it versus the negative impact for those who don't need it. I personally am not convinced this is a feature that would be commonly used yet it would probably take up valuable space in the already crowded interface which we're actually trying to simplify further. As the state of your theme being collapsed or open on a per user basis is remembered, I feel one would very rarely need this feature.

If others feel this Iis a valuable addition please add your comments here and we'll prioritise finding a solution for this.