Move beetwen columns.

[David T.]

Hello all,

I'm trying to move histories between column but, it's acting in a
strange meaner because I can't move from chilly_bin to backlog
directly. What is the reason for that? Can anyone explain me how work
this feature.

Thanks in advance.

[malclocke]

Hi David,

That's almost certainly a bug.

Do you get any errors in the Javascript console of your browser when
trying? In particular do you see 'Unable to determine previous or
next story id for dropped story'?

Malc

[David T.]

On 20 dic, 08:15, malclocke <m...@wholemeal.co.nz> wrote:
> Hi David,
>
> That's almost certainly a bug.
>
> Do you get any errors in the Javascript console of your browser when
> trying?  In particular do you see 'Unable to determine previous or
> next story id for dropped story'?

Hi, thank you for reply.

No, I don't see this message always that it is failing.

If you have all stories in "in-progress" (2 in my case) you can move
into backlog but it is not possible if you have any story in "chilly-
bin". Chilly-bin has to be empty, then you can move into backlog, it's
weird.

You have in the story_view.js a "moveColumn" function that you isn't
using. Is this function planed to be used for something?

I spent several hours searching the bug with no result, sorry. I think
reordering is causing that, but what is determining the stories's
column target when fetching?

Thank you very much again for your help, will be appreciated.

Regards.

[Edwin Cruz]

Hi david, it happened to me when I was upgrading my fulcrum installation, and the problem was that some migrations were missing, I know it sounds trivial, but you could just run db:migrate to be sure that it's not the same case as mine was.

--
Edwin

Sent from my iPhone

[David Teyssiere]

El 20/12/2011, a las 14:59, Edwin Cruz escribió:

> Hi david, it happened to me when I was upgrading my fulcrum installation, and the problem was that some migrations were missing, I know it sounds trivial, but you could just run db:migrate to be sure that it's not the same case as mine was.
>

Hi Edwin, sorry for my late answer.

No luck, the migration was not the problem.

I have reinstalled fullcrum and the problem persist.

Anyone knows what could be the problem or would give me a start point to research?

Thanks in advance.

Regards.

[Malcolm Locke]

On Mon, Jan 09, 2012 at 03:03:22PM +0100, David Teyssiere wrote:
> El 20/12/2011, a las 14:59, Edwin Cruz escribi�:

>
> > Hi david, it happened to me when I was upgrading my fulcrum installation, and the problem was that some migrations were missing, I know it sounds trivial, but you could just run db:migrate to be sure that it's not the same case as mine was.
> >
>
> Hi Edwin, sorry for my late answer.
>
> No luck, the migration was not the problem.
>
> I have reinstalled fullcrum and the problem persist.
>
> Anyone knows what could be the problem or would give me a start point
> to research?

Apologies to everyone affected by this bug, I've finally tracked it down
and pushed what is hopefully a fix
(https://github.com/malclocke/fulcrum/commit/41d15b4e800890eb9f3839df504e136ec50178c6)

The bug is quite subtle, but does manifest itself on the example project
from a completely fresh Fulcrum install. As far as I can tell, the bug
would only occur when:

- The project has no 'started', 'delivered' or 'accepted' stories.
- The project has at least 1 unstarted story in the 'In progress'
column.
- The user tries to drag a story from the chilly bin to the empty
backlog column.

The bug was basically caused by story.column() returning the wrong value
for stories in the 'In Progress' column with state 'unstarted'.

If anyone is still seeing this bug after pulling the commit above please
let me know.

Malc