Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed unnecessary gibberish and repetitions

The Scheduler plugin is designed for automatic issue creation . It allows to define Scheduled Issues that will automatically create standard JIRA Issues at selected at desired time, date or in chosen intervals. Scheduled Issues are able to create standard issues, issues with defined sub-tasks and sub-tasks with selected existing issue as parent.The Scheduler supports all Issue Types, field types and custom fields (except the Attachment field, which is not supported yet.). It means that The Scheduler works with Agile and Service Desk projects, chosen interval, after certain workflow issue transition or when you need this task to be created with manual execution!

Our app supports all Jira issue types with almost all fields available on create issue screen (attachment field is not supported). Beside creating a single issue, you can schedule creating issue with subtask, or just a subtask to already existing in Jira issue.


How does it actually work?

The Scheduler is based on the idea of Scheduled Issues - a template are just like templates for newly created issues. Every project in your JIRA Jira can have its own Scheduled Issues. You can create Scheduled Issue going through easy 3 step wizard starting from "0" and filling all the details or just by scheduling already existing in Jira issue - this way all issue details will be filled in the wizard for you (to speed up the process). For each Scheduled Issue on the 1st step of the wizard you can define Issue Type and fields values (fields set set additional details like name and description - to describe what is for.

Each of Scheduled issues uses fields set from create issue screen is the same like during manually creation issue in JIRA, except the Attachment field). The Scheduler supports dynamically generated summary and description fields from build in variables (like Jira (except mentioned earlier attachments). You can use build in predefined variables (dependent on creation / due date) . If you want, you can also automatically increase issue priority after creating first issue instead of creating more copies.Each Scheduled Issues can contain triggers and dynamically place them in summary and description fields. 

Scheduled Issue can have multiple triggers set, that will create new issues from templates at selected time or intervalwhen the time comes. You can define triggers using The Schedulers on 3rd step of the wizard, for that you can use simple built-in wizard or you can also define more advanced creation conditions by using standard Cron Expressions. You can define multiple triggers for each Scheduled Issue.

Scheduled Issues are assigned to the project, therefore in each project you can see only Scheduled Issues created for that project. Creator of the Scheduled Issue can manage its access rights, as by default only the creators can edit or delete Scheduled Issues. There is one exception - JIRA but Jira Administrators can manage all Scheduled Issues.

JIRA Jira Administrators can set plugin access permissions to allow creating Scheduled Issues for the specified roles, groups , or single users and the Project Lead.You can backup your Scheduled Issues to restore them later on the same instance using import/export function.


The Scheduler supports JIRA clustering, therefore it can be installed on large production systems. Feel free to contact us in case of any issues with The Scheduler under the e-mail or by creating issue on Bitbucketwas designed to be fully Data Center compatible.