The Scheduler gives you great opportunities to configure the Scheduled Issues ​​for your needs. However, this tool also provides a lot of control. One of the indicators for Scheduled Issues monitoring is the “state”.

SI states help recognize what is happening with Scheduled Issue before we enter SI details or upcoming executions. States are visible in the SI table in a “State” column so it enables filtering out invalid templates and fixing them quickly.

The state is clear, simple information that enhances predictability and makes it easier to keep SI table clear.

• Active

• Inactive

• Pending

• Skipping

• Calendar Day Off

• Expired

• Invalid/Failed

• Incomplete

Active

Once created, the Scheduled Issue receives an “Active” (1) state by default. This means that job is configured without any errors and ready for manual or automatic executions (2).

Open

“Active” state in Cloud

Inactive

The “Inactive” (1) state is a great option to keep a template that will not generate new issues, without interfering with its configuration or trigger settings. This allows saving Scheduled Issues in your SI table that have been already executed or will be executed in the future.

Template can be easily inactivated using the buttons “Deactivate” (“Disable” in Cloud) (2) and “Activate/Deactivate” (3) in bulk actions (“Enable/Disable” in Cloud).

In Data Center Scheduled Issue can also become inactive right after creation when the “Set the scheduled issue to inactive after edit” option is selected during creation.

When the state is inactive you do not see any upcoming executions.

Open

“Inactive” state in Data Center

Skipping

One of the trigger settings is “Skip next execution after manual execution”. This feature is useful when you want to maintain flexibility in your Jira. Thanks to this, a new issue can be created manually at any time before the automatic execution and the automatic execution will not be performed. This prevents unwanted duplicates.

Using the above function, when the user runs a manual execution, the next scheduled automatic execution along with the entire SI will change state to “Skipping” (1) and will not be run (2).

Calendar Day Off

Triggers can be configured in relation to the project (2) or global (3) calendar. Calendars are assigned to an SI on the third step of the SI wizard or during triggers editing.

You can read more about calendars here: https://psc-software.atlassian.net/wiki/spaces/SCHED/pages/203816973

When execution falls on the same day as the calendar event it changes the status to “Calendar day off” (1). This status means that the execution planned for that day will be omitted, not fired at all.

The next execution will take place accordingly to the list of upcoming executions.

Pending

“Pending” state (1) occurs when the start date of executions (2) is set in the future. It helps recognize which Scheduled Issues are currently not fired but which are valid and planned to be active in the future (3).

It is possible that template with Pending status will have records in the execution history. Scheduled Issue that has been executed but whose triggers were modified and whose start date was set for the future will have executions recorded in history.

This state relates only to automatic executions. Therefore manual execution of SI before the planned start date does not change the “Pending” state into “Active”.

Expired

Scheduled Issue can expire if you have defined a trigger end date (the default setting is set to never expire). The "Expired" state (1) indicates that according to the trigger definition, this Scheduled Issue usage has ended. That being said, you can still execute this Scheduled Issue manually (2), or edit it (3) to modify the trigger so that the Scheduled Issue can be executed again automatically.

Invalid/Failed

Invalid issue state denotes that for some reason, The Scheduler failed to execute and create the issue. Whenever an "Invalid" (1) state is reached, you need to manually fix the Scheduled Issue by simply editing it and providing the required fields. Once you do that, the Scheduled Issue will get "Active" again and will start working again.

The easiest method for fixing scheduled issues marked with an "Invalid" state (1) is to simply press the "Fix" button (2) and in the three-step wizard, correct the faulty value.

The quickest way to determine the core of the issue is to hover the mouse cursor over the "Invalid" state. By doing so balloon prompt will be presented:

Incomplete

“Incomplete” state (1) means that the execution of particular SI has been completed only partially. Unlike failed Scheduled Issues, a template with an “Incomplete” state can be executed again manually or automatically. However, they will be consequently created with the above state.

A convenient way to fix this is to click on the Fix (2) link that will redirect to the Scheduled Issue wizard and edit the incorrect value.

The Scheduler provides you information about the cause of faulty execution in the balloon prompt (3). Information is displayed every time when the cursor hovers over the incomplete state.

In The Scheduler for Data Center incomplete state can be noticed only in the execution history (2). In the SI table, incorrect issues are marked as Active (1).