Moving cards

Moving a card on GitGumbo changes the real issue on GitLab or GitHub. What it changes depends on what the columns mean: a label, a person, a milestone or, on GitLab, a status.

Who can move cards

You can move cards when both of these are true:

• the account the board runs on can write to the project (on GitLab, its token needs the api scope; on GitHub, a classic token needs the repo scope);
• your own GitLab or GitHub role lets you edit issues in that project.

Your role in the GitGumbo firm doesn't matter here. If the board's token can't write, cards don't drag, and a notice above the board says which scope is missing and how to fix the token, on GitLab and on GitHub. See Linked accounts and tokens.

Drag and drop

With a mouse, pick a card up anywhere and drop it in another column. The drag starts once you've moved a few pixels.

• Drop it on empty space and it goes to the top of the column. On a filtered board, a column whose cards are all hidden looks empty; a card dropped there still goes above the hidden cards, so it is at the top once the filter is off.
• Drop it on a card and it goes just before or just after that card, depending on which half you drop on.

The card moves straight away while GitGumbo writes the change. If the write fails, it snaps back and a "Couldn't move that card" message says why. Teammates see the move on their next refresh (every 5 seconds on Pro, every 30 on Free).

There's no dragging on touch screens and no keyboard dragging. Use the move menu instead.

The move menu

The up-and-down arrows button on a card (Move this card) moves it without dragging. Pick a column, then where in it the card should go: Top, After #N or Bottom. Picking Closed closes the issue. Screen readers announce each move.

The button is always there on touch screens. With a mouse, turn on Settings → Accessibility → Move cards without dragging. In an expanded column (Expand column (for screenshot)), where you can't drag, it's always there too.

What a move changes

Label columns. This covers GitHub boards built from Stage:: labels and GitLab boards whose lists are all labels. The old column's label is removed and the new column's label is added. Other labels are left alone.

GitLab boards with status, assignee or milestone lists. GitGumbo does what GitLab's own board does:

• Into a label list: from another label list, the label is swapped. From a different kind of list, the label is added and nothing is removed.
• Into an assignee list: that person is added to the issue. Other assignees stay, unless you moved it from another assignee list, in which case that person is replaced.
• Into a milestone list: the milestone is set.
• Into a status list: the status is set.
• Out of a status list into another kind of list, the status stays as it is. GitLab requires every issue to have a status.

Because a card can now match two lists, it shows in whichever of them sits furthest right on the board. Sometimes that means it doesn't stay where you dropped it.

GitLab only offers assignee, milestone and status lists on its Premium tier and above.

Your columns (GitHub). For each kind of column involved, the value the old column stands for is cleared and the new one is set. Moving from one label column to another swaps the labels. Moving into an assignee column adds that person and removes any other person who has a column. Moving into a milestone column sets the milestone. Labels, people and milestones that no column uses are left alone.

Open only collects issues that match no column. The move menu doesn't offer it, and an empty Open column doesn't take drops.

Closing and reopening

Drop a card on Closed, or pick Closed in the move menu, to close the issue.

• GitLab: the labels behind the board's lists are removed when an issue is closed, as on GitLab's own board. To reopen, drag the card out of Closed into a column; it's reopened and given that column's value.
• GitLab Status columns: closing a card that sits in a Status column also changes its status, to your project's default closed status: Done, unless your group has customised its statuses. GitLab sets it, and GitGumbo reads it back straight after closing, so the card shows the new status on the board's next refresh.
• GitHub: labels are kept when an issue is closed. Closed GitHub cards can't be dragged out; reopen the issue on GitHub and it returns to its column.

Assignees and milestones are kept on both.

Card order within a column

Drag a card up or down within its column to change its place. With a mouse, the six-dot grip shows where to grab.

• GitLab: this changes GitLab's own issue order, so everyone sees it, on GitGumbo and on GitLab.
• GitHub: GitHub has no issue order, so your order is kept for you alone.

Pins are separate: 📌 keeps a card at the top of its column above any sort, newest pin first, and only you see your pins. Pinned cards can't be reordered.

After a move

If you've set up a column automation for the column, it runs; see the Column automations guide. If you move a card with a draft merge request into a column you haven't set up, GitGumbo may offer to set one up. Set this up and No thanks both stop the offer from coming back.

Sometimes the move works but GitLab or GitHub refuses something that comes with it, such as placing the card at the top of the column, or an automation step. If it refuses for lack of permission, or rejects the token, the card stays where you put it and a Card moved note says what was refused.