Change many jobs at once

Change a selection of jobs

1. Tick the rows on the Jobs tab. Shift-click another row to select it and every row in between.
2. Change Status, Group, Tags or Archived in one of the selected rows — or pick what to do in the Actions menu.
3. The change applies to every selected row.

In the Tree view, each group, site and folder row has a select-all box of its own: stacked boxes in teal, a different shape from the rows' own boxes. It opens the row and selects every job shown under it, and clicked again clears them. A minus in it means some of them are selected. Tick a group's box and use the Actions menu to change every job in the group.

Ticks stay, actions take what you see

A ticked row keeps its tick when a filter hides it, under a closed group, and when you go to another tab and come back: show it again and it is still ticked. But an action only ever takes the ticked rows on screen. The Actions tooltip says how many are ticked there, and how many more are hidden and left out. The same holds on the Run History and File Issues tabs.

The tip under the table explains all this. Once you know it, its × hides it for you; Show hidden messages again on the Settings tab brings it back.

In the Tree view, a row can also be dragged onto another group to move it there; with several rows selected, the whole selection moves.

Jobs that cannot take the change stay as they were, and the notification says how many: a job that is not validated cannot be set to Ready, and a job SMART Migration has already started keeps its status.

The Actions menu

As soon as a row is ticked, Actions appears above the tick boxes, at the start of the column titles — a menu of what can be done to the ticked jobs; its tooltip says how many are ticked:

Action	What happens
Edit / … runs / Copy	Opens the job, its runs on the Run History tab, or makes a copy of it — with just one job ticked.
Copy link	Copies a link that opens the job straight away — with just one job ticked.
Show imported jobs	Shows the jobs the ticked Import jobs created, in the groups they filed them under.
Change selected jobs …	One dialog for every property the ticked jobs share — see below.
Cancel job	Asks SMART Migration to stop the ticked job that is Running — one at a time.
Delete …	Deletes the ticked jobs after you confirm.

Change selected jobs …: every property in one dialog

Change selected jobs … opens one dialog for the ticked jobs. It has the same name in the Actions menu, a row's menu, the Status column's menu and the pinned summary card — there it acts on the ticked jobs the row is part of — and is greyed out until two or more jobs are ticked: one job is changed in its own dialog, with Edit. It is greyed out too while a Job Import is among the ticked jobs: a Job Import is changed on its own, with Edit — untick it to change the rest together. Each property has a row of its own with a switch. Off, the row is quiet and says what the jobs have now — Stays as it is — or Mixed when they differ. Switched on, it opens the property's control, turns green and says Will change — the Tags row with what it will do, such as +Wave 2; a status or a tag still to be picked shows Pick what to set in amber, and Apply waits for it. Under the rows, a green box lists what Apply will set; Apply sets it all at once, on every ticked job. Each change says in its own message how many jobs it changed.

Property	What happens
Status	Hold, Ready or Deferred for every job not yet started; Ready only for the validated ones. Run now sets every validated, enabled job to Ready and puts it first in the queue, ahead of every other job whatever its scheduled date and priority.
Enabled	Disable or Enable: every job keeps its status, but SMART Migration skips disabled jobs until they are enabled again. Applied before the status, so Enable with Run now runs a job that was disabled.
Scheduled Date	Switch it on and pick a date: every job not yet started gets it.
Mode	Discovery, Test Migration or Migration for every job — how a discovered wave becomes a migration.
Destination Type	Nextcloud Team Folder or Nextcloud User: where every job writes its files.
Nextcloud Team Folder	The team folder every job writes into. Left blank, it is cleared on every job, and the jobs whose Destination Type is Nextcloud Team Folder do not validate.
Destination User	The Nextcloud user whose files every job writes into. Left blank, it is cleared, and the jobs whose Destination Type is Nextcloud User do not validate.
Destination Folder	The folder inside the team folder or the user's files. Left blank, the files go to the top of it.
Rules for adding and overwriting files	What every job does with a file already at the destination — see Rules for adding and overwriting files.
Group	Switch it on and pick a group — or none — to file every job under. Manage groups adds one.
Tags	Pick how the tags in the box are applied: Set — every job gets exactly those tags, its others taken off; the box starts with the tags the jobs carry, each once. Merge — the tags you list are added to every job, which keeps its own. Remove — the tags you list are taken off every job, which keeps the rest. When the tags listed would change no job, a green line under the box says so, and Apply waits.
Notifications	Switch it on to set the four boxes — Job start, Job finish, First warning, First error — and Notify to on every job, in place of each job's own. It starts with the jobs' users and groups when they share the same ones, with you otherwise; a box can be ticked only with someone chosen.
Pinned	Pin or Unpin: keeps the jobs at the top of your table, or puts them back. Your own, as every pin is.
Archived	Archive or Take out of archive: applied last, after the confirmation that asks about the jobs' Run History rows.

A job SMART Migration has started keeps its status, date, mode and destination: the switches reach it when the run is over.

Every job is validated again

Apply checks every ticked job against the same rules as the job dialog, as the change leaves it — a mode switched to Migration with no Nextcloud Team Folder named, for instance, does not validate. A job that does not validate is marked Not validated and cannot be set to Ready; one that was Ready goes back to Hold, and a message says how many. Open such a job to see which fields need attention, or filter on Not validated under Readiness. A job the change leaves as it was keeps its own validation unless the rules now fail it. A mode changed here follows the job dialog: a Finished job goes on Hold, since its result belongs to its old mode, and a job on Hold whose latest run of the new mode finished is Finished again, with that run's result — a message says how many of each, and a status picked in the same change is set after it. See Job status

Delete … keeps jobs that are Running or Canceling, or Ready and not disabled; the confirmation lists what will be deleted and what will be kept, and, when the jobs have Run History rows, offers to delete those with them — ticked to begin with; their data then leaves the Business Intelligence data, which the Dashboard shows.

This is the quickest way to release a whole migration wave: tick its group's box, check its jobs, Change selected jobs … with Ready under Status, and the SMART Migration server works through them, four at a time.

A group or location row's menu

The ⋯ menu on a row of the tree does not act on the jobs — the Actions menu does that:

Action	What happens
Show only this group	Sets the Group filter to this group, on the Jobs, Run History and File Issues tabs alike. The other filters stay as they are.
Show only this location	On a site or folder row: puts its path in the Filter box, so only the jobs under it show. Run History and File Issues have it too.
Rename group … / Delete group …	Renames the group, or deletes it together with its jobs and its Run History rows, after a confirmation that counts them.

Find and clear up duplicates — jobs, runs and file issues

Running the same import twice, copying jobs by hand or running a job again can leave rows that say the same thing twice. Jobs, Run History and File Issues each have a Duplicates filter, in the tab bar beside the count of rows shown, that finds them — ignoring case — and a Select duplicates button that ticks them, ready for whatever should happen to them.

Tab	What counts as a duplicate	Kept unticked by Select duplicates
Jobs	Same Title, Same Source or Same Destination	One of each set: a Running, Canceling or Finished job when the set has one, otherwise the oldest
Run History	Same Title (the title without the run's number), Same Source, Same Destination, or Same Job: the runs of one job, found by the job itself whatever its title says now	The first of each set: the oldest, unless a column sort puts another first
File Issues	Same Filename, Same path, or both: the same file reported more than once	The first of each set

1. Pick what counts as a duplicate

   Open Duplicates in the tab bar and pick the column. Only the rows that share it with another are shown; in the list each set sits together, the oldest first.

2. Tick the duplicates

   Select duplicates — red, just left of the Duplicates filter once a choice is picked there — ticks every duplicate except the one kept of each set. Untick any you want to keep, or tick others by hand.

3. Choose what happens to them

   Use the Actions menu on the ticked rows: Delete … to remove them, or Change selected jobs … to file them in another group, archive them or tag them for later. On Run History, Change selected runs … sets the runs' group, tags, pin and archive; File Issues has Pin, Unpin and Delete ….

Duplicate runs are usually re-runs

A job run several times leaves runs with the same title — apart from each run's number — source and destination: they are its history, not mistakes. Delete a run only when it really is one twice over, such as a test run; to clear the clutter of a job's earlier runs, archive them instead — archiving keeps their data in the BI report, deleting takes it out.

Readiness: which jobs can run

The Readiness filter shows whether jobs can run: Validated, Not validated, or Disabled — which SMART Migration never picks up, whatever their status. Running, canceling, canceled and finished jobs are left out of the first two. Use it before a release to find the jobs that still need work.

See also

• Job status
• Groups and tags
• Find your way around the app