---
metadata:
  - name: generator
    content: Diplodoc Platform v5.48.2
alternate:
  - https://admin.contest.yandex.ru/docs/en/contest/problems.md
  - https://admin.contest.yandex.ru/docs/ru/contest/problems.md
---
> **Documentation Index:** Fetch the complete configuration index at https://admin.contest.yandex.ru/docs/en/llms.txt

# Problems

When creating a contest, an empty problemset is attached to it. You can add problems to this problemset or select a different one.
To add problems to the attached problemset:
1. Go to the contest settings page and select **Problems** on the left.
2. Click the problemset name. The [Problemset settings](https://admin.contest.yandex.ru/docs/en/problem-set/settings.md) page opens.

To select a different problemset for the contest:

1. Go to the contest settings page and select **Problems** on the left.
2. Click **Select another problemset**.
3. Select a problemset from the list and click **Add**.
4. Click the problemset name. The [Problemset settings](https://admin.contest.yandex.ru/docs/en/problem-set/settings.md) page opens.

## Statements {#statements}

On the **Statements** tab, you can view the list and statements of the problems added to the problemset. To go to a problem's settings, click its name.

To view the statements, click ![](../_images/contest/00_preview_icon.png =30x) next to the problem. The statements will open in the new tab.

## Testing {#testing}

On the **Testing** tab, you can view detailed information about added problems. All data is only available for viewing.

To go to a problem's settings, click its name.

## Problem visibility rules {#visible-rules}

On the **Task visibility rules** tab, you can set the order of and conditions for displaying problems.

The rules are set in a JSON file and uploaded by clicking **Select file**. After uploading the rules, you can download them or view them under the download button.

The JSON file must have one `rules` object: an array with rules for each problem. Problem fields:

#|
|| **Field name** | **Description** ||
|| `problem`| This is a **required field**.

Short problem name.||
|| `visibleSince`|Show the problem after the specified number of milliseconds from the start of the contest. ||
|| `visibleDuring`| Hide the problem after the specified number of milliseconds.||
|| `hideWhenSolved`|Hide the problem if it's solved:
* `value`: Enter `true` to enable this option.
* `scope`: How to hide:
    * `local`: When the problem is solved by the current user.
    * `global`: When the problem is solved by any contest participant. ||
|| `hideWhenAttempted`| Hide the problem if attempts were made to solve it (see the `hideWhenSolved` field).||
|| `shouldBeSolved`|Show the problem when other problems are solved:
* `value`: List of short problem names.
* `quantifier`: A method for applying the rule:
    * `all`: When solving all the problems from the list.
    * `any`: When solving at least one problem from the list.

* `scope`: Hiding type:
    * `local`: When problems are solved by the current user.
    * `global`: When problems are solved by any contest participant.||
|| `shouldNotBeSolved`| Show the problem when other problems aren't solved (see the `shouldBeSolved` field).||
|| `shouldBeAttempted`| Show the problem when attempts were made to solve other problems (see the `shouldBeSolved` field).||
|| `shouldNotBeAttempted`| Show the problem when no attempts were made for other problems (see the `shouldBeSolved` field).||
|#

> **Example**
>
> This configuration shows problem A from fifteen to thirty minutes after the start of the contest, hides it after it's solved, then shows problem B after at least one contest participant solves problem A.
>
> ```json
> {
>   "rules" : [
>     {
>       "problem" : "A",
>       "visibleSince" : 900000,
>       "visibleDuring" : 1800000,
>       "hideWhenSolved" : {
>         "scope" : "local",
>         "value" : true
>       }
>     },
>     {
>       "problem" : "B",
>       "shouldBeSolved" : {
>         "scope" : "global",
>         "value" : [ "A" ],
>         "quantifier" : "all"
>       }
>     }
>   ]
> }
> ```

<!-- source: en/_includes/reusables/support-button.md -->
<a href="../../troubleshooting">
  <span class="button">Write to Support</span>
</a>



<!-- endsource: en/_includes/reusables/support-button.md -->