App descriptions, when different will be divided Cloud / Server & Data Center.
Server & Data Center
Thank you for choosing The Scheduler!
On this page you will learn how to configure app and how to start using it to its fullest potential.
We will cover:
Some of the features
Documentation, Support & Feedback
The Schedulers main job is the create Jira issues - on scheduled time. It allows easily create tasks in future through simple 3 step wizard. Scheduling options are quite flexible, with different types of triggers you can schedule issue creation every 2 weeks, 2 month or even with use of advanced cron expressions. All depending on your needs.
Wizard compose of 3 steps:
Scheduled Issue details - name, description - place to describe the template (searchable in SI table, describe it well)
Issue details - fields from create issue screen for particular project and issue type. If you are missing fields please check if those appear on Jira create issue screen
Triggers - when issue should be created, there are many types of triggers available
One of the usage of app is templating - keep issue details in template and create task when needed. For that you can use Manual triggers (or any other trigger type), and use “Execute” option when needed. Eg. Your onboarding process can be scheduled as Task with certain Subtasks.
By default Jira Administrators and Project Administrators have access to all Scheduled Issues in project. But app can be configured to allow certain Jira users to use the app and schedule issues. It is managed with global and project permissions.
Custom permissions created by app:
Global: The Scheduler: Access This global permission is required for users to access the app on global level. Project and Global Administrators are granted this by default. This permission is like an app wrapper, on project level users are required to have permission “The Scheduler: Use”.
Project: The Scheduler: Use Granting this permission allows to use the app for creating scheduled issues (create, edit, view, delete). Project and Global Administrators are granted this by default - to ensure app can be used and managed. Global permission “The Scheduler: Access” is required.
When user is granted with app permissions, new option “Scheduled Issues” will appear on the project sidebar:
On existing Jira issue, new option ‘Schedule Issue’ will be available in more actions:
Besides Global Calendars, The Schedule is managed on project level, where project administrators can grant access to app, set up Project Calendars and set up failure Notifications.
Within notifications section they can decide who will receive notification of failures eg. issue is not created, and fallback if this notification cannot be send. This feature allows to make sure that even if the task is not created → right person is informed and can take action to fix the Scheduled Issue or create a task manually.
In the Manage apps → The Scheduler section on the left taskbar → Global Settings <as link>, you can find configuration options, which will have impact for the whole application. eg.
Limit the number of displayed issues in: execution history, upcoming executions or failed executions log.
Change some off the options and allow/block overriding those in project settings.
Default Share Settings
Scheduled Issues are private by default, but with default share option you can share newly created Scheduled Issues with chosen groups, users, roles or all Jira users (to allow them editing). Sharing also can be done on single issue or in bulk, but this option expands access to SI by default.
If you need to add date in the summary, description (or any other text field) you can use Predefined variables. Those are variable which depends on creation or execution date and can be converted to the corresponding values on issue creation. Here you can find table with available variables and usage examples: https://psc-software.atlassian.net/wiki/spaces/SCHED/pages/827719763
In Jira fields like due date are static - fixed to 1 date, within our templates you can link due date with task creation date eg, make it dynamic with 2 weeks from creation date, or link it with next execution time, this way task should be done before new one gets created.
There are some features like <initial issue status> which can help you in managing your tasks visibility on kanban board. It might also help in templating eg. when you execute scheduled issue it will change into your chosen status eg. ‘in progress’
In Server (& Data Center) be aware that some of the pages might be outdated or the view might have changed. In documentation page tags you will see the version number in which new feature was introduced.
If case of any issues with the app, or if you have ideas for new features or improvements, please let us know by creating a ticket on our Customer Portal
If you think you found a bug, please describe the behaviour and steps explaining how to reproduce your problem - we will do our best to fix it. To speed up the process, in the initial contact please include:
Each day, we are working to improve our app by bring new features. If you like it or if it saves you time, help us by letting other Jira Admins to know about it. You can do it by leaving a review or feedback on marketplace. We really appreciate it, it gives us a boost