Import from another space

A problem in one of your other spaces can be copied into this one. Spaces are otherwise separate, and this is the way a problem crosses between them — the copy becomes an ordinary problem of the receiving space, editable and independent of the original.

You need permission to write problems in the space you are importing into, and access to the problem in the space you are importing from.

1. Open the console and switch to the space the problem should go into.

2. Go to Problems.

3. Click Import from a space.

4. In Space, pick the space to copy from. Only spaces you have access to are listed.

5. In Problem, pick the problem within that space.

6. Confirm.

The problem is created immediately and copied in the background; the source problem's public URL is recorded as the copy's origin. Follow it on the problem's Activity tab, or in Background tasks. The copy starts unpublished and takes the next number in the receiving space's catalog.

Unpublished problems can be imported too, as long as you have access to them in the source space.

What may be missing

Content marked secret in the source problem — tests, checkers, interactors, generators, templates — is not sent to the console, so it cannot be shown or copied out. You can put your own in its place with Override. See Import problems.

Keeping it up to date

Synchronize, in the problem's row menu or its header, pulls the source problem again and replaces your copy with it — local edits are overwritten and cannot be recovered.

Synchronization runs as the person who clicks it. If that account has no access to the problem in the source space, the synchronization fails, even though the import originally succeeded for someone else.