Tickets added to the bottom of the list?

[seanlinsley]

As far as I can remember, when a ticket was moved between columns historically, it'd always default to be at the top of the list, unless you dragged it to a specific spot. That no longer seems to be the case, and instead tickets are added to the very bottom of the given column. Was this change intentional? Is there any chance we could introduce a setting to add back the original behavior?

[discorick]

Hey @seanlinsley, do you mean when you are dragging a card to any blank space at the very of the bottom of the column ?

[dahlbyk]

Following up on this, @seanlinsley. Is this still an issue for you? I can't speak to whether this was an intentional change in behavior, but we do seem to consistently place cards at the bottom when dropped into the empty space below a column.

That said, it would be nice to be able to send issues to the top of a column, as you can in JIRA.

[seanlinsley]

It seems to behave a bit differently now. Clicking the status names inside the modal cause the card to be moved to a position relative to its previous position in its previous column. For example if it was at the first position in the previous column, it'll move to the first position in the new column. If it's third, it'll move to third (or sometimes fourth) in the new column.

[dahlbyk]

Ah, so you mean moving into a column without dragging. I would guess we're simply applying the issue label (same as if done manually in GitHub) without touching the order value. @discorick has that ever not been the case?

[discorick]

I honestly can't remember @dahlbyk - I could be persuaded that relative order between columns is not the ideal default though.

[dahlbyk]

Well "reusing" order across columns will happen for items adjusted directly in GitHub whether or not we choose to do otherwise for changes made from our issue modal. Another angle would be to update our order calculation to work toward the columns being sorted relative to each other (e.g. bottom of column 3 has higher priority than top of column 2). This would make the "dragless" card moves somewhat more deterministic (left to right appears at bottom; right to left at the top), though we still wouldn't be able to make 100% guarantees.