Changing several tickets at once

When many tickets need the same change, you do not have to open them one by one. You tick them in the list and put the change together once.

How it works

1. Go to the project's ticket list and filter it until it shows what you want to change.
2. Tick tickets: one by one with the box before the number, several in a row with Shift held, or every loaded row with the box in the table head. When the page is full and the list has more hits, the row above offers select all N.
3. With the first box the panel Edit N tickets opens on the right. It starts empty: only what you add is changed.
4. Click Change a field and pick a field. Under every field you see what the selected tickets carry today, for example so far: in progress 8 · open 6.
5. Set the value. For tags, assignees and watchers you can add values (plus) and take them away (minus), both in the same row.
6. The button Change N tickets executes. Nothing happens before that.

The result then stands above the list, for example Status set to "in progress" · 14 tickets changed. The selection stays, so you can add the next change right away.

When not everything works

If a ticket cannot take the change, the others are changed anyway. The result line then says 12 of 14 changed · 2 could not be changed and names the two. If somebody changed one of the tickets in the meantime, nothing is written; you see the current stock and can execute again.

Undo

Next to the result, Undo is offered for 24 hours. It restores exactly the tickets the run changed and nobody touched since. You also find the run as one line in the project feed.

Moving and deleting

Under the button sit the other actions, each with its own confirmation:

• Move to another project: you choose the target, and the dialog says beforehand what the move takes with it: assignments and followers without access to the target project are lost; time entries move along. Tickets with sub-tasks or a parent ticket stay here and are named in the result. The tickets get new numbers in the target project, which is why there is no undo.
• Delete: the dialog counts what goes with the tickets (comments, attachments) and what stays behind (time entries keep their booking but lose the ticket; sub-tasks become standalone). Deleting cannot be undone.

Both actions need the respective right (move tickets, delete tickets); without it the row is missing. Afterwards the selection is empty, because the tickets have left the list; the result stays above the list until you dismiss it.

What others notice

Every ticket keeps its own entry in its history with the old and the new value. People who follow the tickets get one notification for the whole run instead of one per ticket. The project feed shows the run as one line.