Scheduled Issue Wizard

No matter which option you chose, you'll end up in the "Scheduled Issue Wizard" dialog that allows you to define Scheduled Issue attributes, such as name or description, the Issue Template and define the desired trigger.

The first page of the wizard prompts you for the Scheduled Issue attributes, such as Name and Description. Name attribute is required, and it has to be unique within each project (so that each Scheduled Issue can be easily distinguished from the other). The wizard will notify you if the name you have chosen is already taken.

If a typed name is not unique (in other words - if it has already been used) you won't be able to get to the next step. This is indicated by the red exclamation point (1↖).

The second page allows you to define the Issue Template. In the top section, you choose the issue type you want to create. Once you do that, the bottom section will display the fields that are used by the chosen issue type for you to fill up. The required fields are marked with the "*" and the wizard will not let you through if you leave them empty. Currently, we support all of the Jira standard and custom fields (except the "Attachment" field). Please be advised that it is not possible for us to support any third-party custom field(s), defined by other add-on(s). If you need a particular third-party custom field support, please raise a ticket and we'll see if it's possible for us to handle it.

Selection of a certain "Issue Type" from a drop-down menu (1↗) changes the view of the above presented prompt's content dynamically and reflects fields of a particular issue type in a given project.

The third page is the Trigger details section, where you can define how often your Scheduled Issue should be created. There are three trigger types to choose from: Cron, Interval and Manual (↙1).

Choosing Manual trigger type will let you create a Scheduled Issue without a Trigger. As described in "Manual Scheduled Issues" section, The Scheduler will not attempt to create this issue periodically, but instead, such a Scheduled Issue can be manually executed with "Execute" action.

Please bear in mind that only scheduled tasks in the "Active" state can be executed. If state is set as "Inactive" (↖2), then "Execute (1↗) action is grayed out.

Cron and Interval trigger types are actually quite similar, in a way that both of them allow you to define a trigger.

Simple trigger type lets you define a trigger with a user-friendly period picker, whereas "Advanced" allows you to provide your own Quartz cron expression. The "Simple" picker contains a number of options that should be sufficient for most of the use cases. However, should you need a truly custom trigger, the "Advanced" type is here to help.

The above image presents exemplary "Simple" (3↑) mode view. Only chosen "Cron" as a trigger type, (1↑) enables mode selection (2↑).

By default, the trigger is always started ("Start Date" is set to "Now"), and it never expires ("End Date" set to "Never").

Besides the actual period, you can also specify the "start" and "end" dates for the Trigger to get into effect. You can modify these dates to fit your particular use case i.e.as presented in the above image, with "Advanced Mode" (↖1) present.