Fixed bugs:
- Do not present any links with JWT in app pages
- Subject of email notification after SI execution is "sum" instead of issue summary
Remember about our: Status Page and Release Notes
Fixed bugs:
Remember about our: Status Page and Release Notes
Improvements, bug fixing:
***
Migrations to Cloud are available only from the latest marketplace version of The Scheduler - we had to make such constraint to ensure stable migrations.
Improvements, bug fixing:
***
Migrations to Cloud are available only from the latest marketplace version of The Scheduler - we had to make such constraint to ensure stable migrations.
Improvements, bug fixing
Migrations improvements:
From now on migrations to Cloud will be available only from the latest marketplace version of The Scheduler - we had to make such constraint to ensure stable migrations.
Improvements, bug fixing
Migrations improvements:
From now on migrations to Cloud will be available only from the latest marketplace version of The Scheduler - we had to make such constraint to ensure stable migrations.
Compatibility with Jira 9.7.0 and minor bug fixes
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Compatibility with Jira 9.7.0 and minor bug fixes
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Improvements
Bug fixing
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Improvements:
Bug fixing:
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Bug fixing
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Bug fixing
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Improvements
Bug fixes
---
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version (currently v1.7.7) or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Improvements
Bug fixes
---
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version (currently v1.7.7) or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Technical release - dependency updates
Technical release - dependency updates
Compatibility with Jira 9.x and minor bug fixes
Compatibility with Jira 9.x and minor bug fixes
Ability to set date fields (like Due Date) in relation to the month of the issue creation: End of the month offset. Option takes default value “0d” - which is the end of the month. You can set offset like 1d, 2d etc, accepted are only positive values. Depending on settings, issues will be created with due date X days before the end of the month of the issue creation.
Other changes:
Ability to set date fields (like Due Date) in relation to the month of the issue creation: End of the month offset. Option takes default value “0d” - which is the end of the month. You can set offset like 1d, 2d etc, accepted are only positive values. Depending on settings, issues will be created with due date X days before the end of the month of the issue creation.
Other changes:
Migration to Jira Cloud
Starting from The Scheduler v6.5.0 you can easily migrate to Jira Cloud, you need to have Jira Cloud instance and installed our app. Here you can read about the process and all the details: Migrating The Scheduler
As always remember to test in testing environment.
In case of any issues, please contact our support with all the details: Support Portal
Bug fixing:
---
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version (currently v1.6.6) or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Migration to Jira Cloud
Starting from The Scheduler v6.5.0 you can easily migrate to Jira Cloud, you need to have Jira Cloud instance and installed our app. Here you can read about the process and all the details: Migrating The Scheduler
As always remember to test in testing environment.
In case of any issues, please contact our support with all the details: Support Portal
Bug fixing:
---
Important! Due to migration app is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version (currently v1.6.6) or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Important! This is pre-migration version and it is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version (currently v1.6.6) or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Note: The Scheduler v6.5.0 will be the version ready for migration to Jira Cloud. Here you can review the main differences: Migrating The Scheduler
Important! This is pre-migration version and it is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version (currently v1.6.6) or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Note: The Scheduler v6.5.0 will be the version ready for migration to Jira Cloud. Here you can review the main differences: Migrating The Scheduler
Important! This is pre-migration version and it is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version (currently v1.6.6) or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Improvements:
Bug Fixing:
Note: The Scheduler v6.5.0 will be the version ready for migration to Jira Cloud. Here you can review the main differences: Migrating The Scheduler
Important! This is pre-migration version and it is dependable on “Jira Cloud Migration Assistant” app. Before updating The Scheduler, make sure to update “Jira Cloud Migration Assistant” to latest version (currently v1.6.6) or remove that app (if you are not planning to migrate to cloud anytime soon). Otherwise, The Scheduler modules will be disabled - app won’t start.
Improvements:
Bug Fixing:
Note: The Scheduler v6.5.0 will be the version ready for migration to Jira Cloud. Here you can review the main differences: Migrating The Scheduler
Bug Fixing:
- Fixed issue with initial status in some specific cases
Bug Fixing:
- Fixed issue with initial status in some specific cases
New features:
Improvements:
Bug Fixing:
Important: Our team has checked The Scheduler for log4j vulnerability - application is not affected.
New features:
Improvements:
Bug Fixing:
Important: Our team has checked The Scheduler for log4j vulnerability - application is not affected.
New feature
Improvements:
Minor bug fixing
New feature
Improvements:
Minor bug fixing
Improvements:
Bug fixing:
Improvements:
Bug fixing:
Improvements:
Bug fixing:
Improvements:
Bug fixing:
Improvements:
Bug fixing:
Note: It might be a good idea to use Integrity Checker to check for duplicated permissions before update, if you are facing issue after update: Fix issue with upgrade v6.4.0
Improvements:
Bug fixing:
Note: It might be a good idea to use Integrity Checker to check for duplicated permissions before update, if you are facing issue after update: Fix issue with upgrade v6.4.0
Custom Jira Permissions - we have been announcing this for a while. Finally v6.4.0 introduces:
Settings from Access Manager (roles, groups and users) will be applied to active permissions schemes into permission “The Scheduler: Use”. Make sure to review and adjust all applied permissions after the update.
Improvements
Bug fixes:
Note: It might be a good idea to use Integrity Checker to check for duplicated permissions before update, if you are facing issue after update: Fix issue with upgrade v6.4.0
Custom Jira Permissions - we have been announcing this for a while. Finally v6.4.0 introduces:
Settings from Access Manager (roles, groups and users) will be applied to active permissions schemes into permission “The Scheduler: Use”. Make sure to review and adjust all applied permissions after the update.
Improvements
Bug fixes:
Note: It might be a good idea to use Integrity Checker to check for duplicated permissions before update, if you are facing issue after update: Fix issue with upgrade v6.4.0
Compatibility with JEditor
Fixed issue with installation on Jira 7.x
---
Access Manager will be deprecated in v6.4.0
We are moving towards Jira permissions on Global and Project level to ease the access management. With upcoming v6.4.0 settings from access manager will be applied to active permissions schemes. Roles, groups and users, will appear in our apps custom permission. To make this a smooth process, we strongly recommend to: move any single users mentioned in access manager to a dedicated access group for app. It would be easier to manage and faster to troubleshoot, if something goes wrong during update, which will take place immediately after update to v6.4.0
Compatibility with JEditor
Fixed issue with installation on Jira 7.x
---
Access Manager will be deprecated in v6.4.0
We are moving towards Jira permissions on Global and Project level to ease the access management. With upcoming v6.4.0 settings from access manager will be applied to active permissions schemes. Roles, groups and users, will appear in our apps custom permission. To make this a smooth process, we strongly recommend to: move any single users mentioned in access manager to a dedicated access group for app. It would be easier to manage and faster to troubleshoot, if something goes wrong during update, which will take place immediately after update to v6.4.0
Jira 8.15.0 Compatibility update
Bug fixing:
--
Access Manager will be deprecated in v6.4.0
We are moving towards Jira permissions on Global and Project level to ease the access management. With upcoming v6.4.0 settings from access manager will be applied to active permissions schemes. Roles, groups and users, will appear in our apps custom permission. To make this a smooth process, we strongly recommend to: move any single users mentioned in access manager to a dedicated access group for app. It would be easier to manage and faster to troubleshoot, if something goes wrong during update, which will take place immediately after update to v6.4.0
Jira 8.15.0 Compatibility update
Bug fixing:
--
Access Manager will be deprecated in v6.4.0
We are moving towards Jira permissions on Global and Project level to ease the access management. With upcoming v6.4.0 settings from access manager will be applied to active permissions schemes. Roles, groups and users, will appear in our apps custom permission.
To make this a smooth process, we strongly recommend to: move any single users mentioned in access manager to a dedicated access group for app. It would be easier to manage and faster to troubleshoot, if something goes wrong during update, which will take place immediately after update to v6.4.0
Access Manager will be deprecated in v6.4.0
We are moving towards Jira permissions on Global and Project level to ease the access management. With upcoming v6.4.0 settings from access manager will be applied to active permissions schemes. Roles, groups and users, will appear in our apps custom permission.To make this a smooth process, we strongly recommend to: move any single users mentioned in access manager to a dedicated access group for app. It would be easier to manage and faster to troubleshoot, if something goes wrong during update, which will take place immediately after update to v6.4.0
Bug Fixing:
Access Manager will be deprecated in v6.4.0
We are moving towards Jira permissions on Global and Project level to ease the access management. With upcoming v6.4.0 settings from access manager will be applied to active permissions schemes. Roles, groups and users, will appear in our apps custom permission.To make this a smooth process, we strongly recommend to: move any single users mentioned in access manager to a dedicated access group for app. It would be easier to manage and faster to troubleshoot, if something goes wrong during update, which will take place immediately after update to v6.4.0
Bug Fixing:
Improvement:
Bug Fixing:
---
Migration survey
We have prepared special survey with questions in areas which might affect the migration process. Please give some insights about your migration perspectives - It will help us to focus on the most important things.
Please fill in the form: https://forms.gle/FcLNZ4WcZDmv4gib9
Improvement:
Bug Fixing:
New Status: Incomplete
We have added a new execution status “Incomplete”, which means that issue was created, but some predefined element is missing. Eg. due to configuration changes once optional field turns to be required - The Scheduler will mark execution as Incomplete - this way, issue will be created on schedule and user can update required data in created Jira issue. Upon edition/creation all required fields need to be filled with valid data. Incomplete status will help in testing new configurations, without the issue of missing issue creation.
Minor bug fixing related to compatibility with other apps.
Migration survey
We have prepared special survey with questions in areas which might affect the migration process. Please give some insights about your migration perspectives - It will help us to focus on the most important things.
Please fill in the form: https://forms.gle/FcLNZ4WcZDmv4gib9
Note: v6.3.5 was reversed, because of an issue with default values not set on some fields
New Status: Incomplete
We have added a new execution status “Incomplete”, which means that issue was created, but some predefined element is missing. Eg. due to configuration changes once optional field turns to be required - The Scheduler will mark execution as Incomplete - this way, issue will be created on schedule and user can update required data in created Jira issue. Upon edition/creation all required fields need to be filled with valid data. Incomplete status will help in testing new configurations, without the issue of missing issue creation.
Minor bug fixing related to compatibility with other apps.
Note: v6.3.5 was reversed, because of an issue with default values not set on fields, which are not visible on create issue screen
Improvements:
Bug fixing:
Improvements:
Bug fixing:
Bug fixing:
Bug fixing:
Improvements:
Minor bug fixing:
Improvements:
Minor bug fixing:
Improvements
Minor bug fixing
Improvements
Minor bug fixing
New features
Improvements
New features
Improvements
New bulk operations: Enable / Disable Scheduled Issues - now you can deactivate issues in bulk
Improvements:
Minor bug fixing
New bulk operations: Enable / Disable Scheduled Issues - now you can deactivate issues in bulk
Improvements:
Minor bug fixing
Version 6.2.3 brings new feature: Ability to skip next planned execution of SI, after manual execution - now if you decide to create task ahead of schedule it can skip next ticket creation! Here you can see an Example: Skip next planned execution, after manual execution
Improvements:
Bug Fixes:
Compatibility update with Jira 8.7.x
Version 6.2.3 brings new feature: Ability to skip next planned execution of SI, after manual execution - now if you decide to create task ahead of schedule it can skip next ticket creation! Here you can see an Example: Skip next planned execution, after manual execution
Improvements:
Bug Fixes:
Compatibility update with Jira 8.7.x
Improvements:
Bug fixes
Improvements:
Bug fixes
New features:
Improvements:
Bug fixes:
New features:
Improvements:
Bug fixes:
New features
Improvements:
Bug fixes:
Survey
We are planning ahead and would like to know about your perspectives with moving to Jira Cloud version. Please fill in short survey: The Scheduler (into Cloud)
In order to deliver faster and better features: We are increasing lower compatible Jira version to 7.3.0 (about EOL).
New features
Improvements:
Bug fixes:
Survey
We are planning ahead and would like to know about your perspectives with moving to Jira Cloud version. Please fill in short survey: The Scheduler (into Cloud)
In order to deliver faster and better features: We are increasing lower compatible Jira version to 7.3.0 (about EOL).
Minor UI/UX Improvements:
Minor bugfixes
Minor UI/UX Improvements:
Minor bugfixes
Improvements:
Bug fixing:
Improvements:
Bug fixing:
Version 6.1 is finally here.
New features:
Improvements:
Bug fixing:
Version 6.1 is finally here.
New features:
Improvements:
Bug fixing:
After pursuing official Atlassian process - we have released fully Data Center compatible version of The Scheduler
After pursuing official Atlassian process - we have released fully Data Center compatible version of The Scheduler
New features:
Improvements:
Improvements:
Improvements:
Improvements:
New features:
Improvements:
New features:
Improvements:
Use our dedicated Customer Portal to report bugs and request new features.
Bug fixing:
New features:
Bug fixing:
Improvements:
Bug fixing:
Exciting Version 5.1.0 !
New Features:
Bug fixing:
We have also refreshed the look of The Scheduler with new icon :)
Fixed Issues:
Issue #250 - Import from version 4.x to 5.x
Issue #186 - Jira System Administrators & Jira Administrators are now able to export all Scheduled Issues
Service Desk compatibility - Issue #140 - you can use The Scheduler with Service Desk (starting from version 3.7.0 - fixed issue: JSDSERVER-1211 ), if you want to set up "Request Type" on issue creation - make sure you have the field "Request Type" set on "Create Issue Screen" (it is not available by default).
Fixed issues:
Fixed issues:
Improvements:
Removed option to import data from The Scheduler versions < 3.x
For Jira Administrators, accessing The Scheduler through "Add-ons" section: In Step 1 of the wizard we linked Creator and Project picker.
Fixed issues:
Compatibility update - Jira 7.4
Fixed issue with assignee/reporter username change - Issue #212.
Fixed issue with ordering sub-tasks with renamed users.
Added translated issue types based on Jira settings.
New feature: Ordering sub-tasks - now you can take full control over order of created sub-tasks!
Fixed Issue #206
Fixed reload on "Custom Date", "Custom Date Time" fields picker.
We are introducing The Scheduler 5.0
Important: If you're upgrading from previous The Scheduler version, we recommend you to upgrade to the latest available version before installing The Scheduler 5.x.
New version comes with new features:
For more details please refer to documentation or contact us using one off available channels
We are open for feedback and ideas!
Jira 7.1.0 is now supported!
New features:
Bugfixes:
4.0.6:
4.0.4:
4.0.3:
4.0.2:
4.0.1:
4.0.0:
The Scheduler for Jira 6.x is back in Atlassian Marketplace!
New features:
The Scheduler now supports a Clustered Jira Environment.
Added validation of Issue Security Field
NEW FEATURES
IMPROVEMENTS
NEW FEATURES
IMPROVEMENTS
BUG FIXES
NEW FEATURES
PERFORMANCE IMPROVEMENTS
OTHER IMPROVEMENTS
BUG FIXES
New in this release
+ plugin compatible with Jira 6.2
New in this release
+ the logic has been improved so that the fire counter and previous fire time are being updated also when firing leads to priority change
+ the logic has been improved so that the log file contains more information about the affected scheduled issue and trigger when any quartz based runtime exception is being thrown
Fixed in this release
+ fixed the bug where The Scheduler created new issue instead of increasing priority of the last one (that have occurred when an user changed the reporter or the summary)
Fixed in this release
Fix added that seriously decreases period of time it has taken between first and second step of create/edit wizard
Fix added that disallow spaming Jira's log files with stack traces from expected exceptions
New in this release
Version fully compatible with Jira 6.1
This release includes small improvement to DueDate field for which value now can be provided in three different ways. As before there are options like Fixed and Dynamic due date value, but now there is also third option "Next Fire Time". When selected indicates that due date field should be populated by next fire time value for scheduled issue.
Fixed in this release
Fixing problem with JavaScript events being not properly handled in relation to scheduled issues tab panel as well as other actions from drop down menu for each scheduled issue (like: fire, enable, disable, delete). After modification navigating between other project tabs doesn't interfere with TheScheduler actions.
Version 3.0.3 also includes couple of UI related corrections mainly connected with presenting information in scheduled issues table.
New in this release
Current version is partially compatible with 6.1. You can use this plug-in with 6.1 but auto migrate (upgrade) process won't be able to migrate your old data from version 2.6.4 and earlier. We are working on solution for this problem.
Fixed in this release
Fixing problem with Reporter being not set to proper value. Currently reporter field is populated by value which was provided during scheduled issue template creation. In case such reporter user doesn't exist anymore or is inactive we are using "Created By" user.
Resolved issue with "Created By" being set to "N/A" value.
Release with couple of fixes for bugs raised from 3.0 release date.
This version fixes the following problems:
1) Problem with old data migration in case of non existing project or issue type.
2) NPE when reporter field is not set (field not visible for current user) and there is "Increase Priority" option checked.
3) Column "Reporter" is set to "N/A" value if we try to create new Scheduled Issue by user without permission to see "Reporter" field.
4) There is error when trying to create new scheduled issue. Problem occures for projects with default issue type set to "None".
5) When creating new issue if you type in more than 4 lines of text into the “Description” field it generates the error.
TheScheduler 3.0 compatible with Jira 6.0
In this version TheScheduler plugin was completely rewritten from scratch to be more powerful.
From now you can create scheduled issues which has as many triggers (Cron expressions) as you like.
Moreover there is ability to constrain each trigger by providing time period (start & end date). This feature allows you to specify more complex points in time when real issues should be created basing on scheduled issue.
Like in previous version you still have option to set due date in one of two formats - fixed & dynamic due date.
Fixed remained unchanged from user perspective but we decided to change dynamic due date format to behave like "Remaining Estimate" field which allows user to enter value in "1w 3d" format.
New Scheduler adds also ability to select which columns should be visible in scheduled issues table view. So you can decide what information has higher priority for you and configure columns exactly as you like.
Version 3.0 uses only one licensing method which is based on Atlassian Marketplace licensing so we no longer support legacy license file. If you already have license file you can contact with us and we try to resolve this problem.
Finally version 3.0 acts as a milestone and gives us ability to provide much more features which implementation would be impossible without complete redesign of our plugin.
This release contains bug fixes to the following issues:
APDC-104 (TSP-46)
APDC-105 (Raised on Atlassian Answers)
TheScheduler 2.6.4 contains a few major bug fixes which resolves problem with
some custom fields provided by third party plugins - becouse not every custom field is intended to be shown (visible by user) there was a problem when plugin wanted to render (dispaly) such fields.
We added additional condition to check if custom field is renderable and if not we just ignore such field.
In this relese we also included fix which causes problem if user want to edit scheduled issue job which never be run again - there was NullPointerException becouse trigger associated with JOB cannot be acquired.
Finally there is one more little security check to ensure that scheduled job template can be created even if "Resolution" field is placed on Create Issue Screen.
This release is fixing following issues:
[TSP-43] All plugin uploads hang forever after Scheduler pro plugin is installed - Problem with disabling/enabling/uninstalling via UPM resolved.
The Scheduler 2.6.2 (build 21)
Version 2.6.2 brings user ability to edit invalid scheduled jobs (highlighted with red background) - such as tasks with missing priority, issue type or invalid real creator.So far, there was only a possibility to delete invalid job.
The Scheduler 2.6.1 (build 20)
Added additional code to perform scheduler database initialization in case user upgraded from TheScheduler 2.5 (with Atlassian licensing) to TheScheduler 2.6.1.
Because version 2.5 with Atlassian licensing doesn't have "LICENSE_INFO" table required by 2.6.1 version we had to add additional initialization code which create such table in case of its absence.
Resolved issue with DELETE/ENABLE/DISABLE - each action contained invalid code which was responsible for checking if license is valid. Unfortunately there was only Atlassian license chcecked so even if user had vendor license file uploaded enumerated actions cannot be performed.
Fixed problem with incorrect link after clicking on reporter/assignee for each scheduled issue template entry. Link was constructed using full name of user instead od just login name.
IMPORTANT! - After installing or upgradeing to new version we recomend deleteing tomcat and also browser cache.
If there is any problem with our plugin make sure that there is no cache leaved for both tomcat and your browser.
If problem still persists then feel free to contact us.
The Scheduler 2.6 (build 19)
New version of TheScheduler (2.6) is now compatible with Jira 5.1 and previous 5.0
You do not need two different version of our plugin to run onto Jira 5.0 and/or 5.1
Sometimes after creating new scheduled issue template user want to check if real issue will be created.
New version now also brings user ability to fire scheduled task at any time by clicking on link "Fire" next to other options for each scheduled issue task.
Becouse many of our existing customers already have legacy license file we decided to release one plugin with two licensing methods.
New Atlassian Marketplace licensing method which is recomended for all new customers, and old one bassing on license file which were in use before we decide to go Atlassian way.
Version 2.6 also fixes problem with Creator field value bieing not saved during "Edit scheduled template" operation (TSP-42).
IMPORTANT! - After installing or upgradeing to new version we recomend deleteing tomcat and also browser cache.
If there is any problem with our plugin make sure that there is no cache leaved for both tomcat and your browser.
If problem still persists then feel free to contact us.
The Scheduler 2.5 (build 18)
Replacing old licensing system with new one provided by atlassian api. New licencing allow transparent management of licensing across many different plugins. From user perspective actions such as renewing license and checking current license status are available from UPM (Universal Plugin Manager) directly from Jira. If for some reason there is no available UPM which supports new licensing system user can use dedicated "License" tab available from the plugin menu.
New licensing system allow user to use plugin as normally only in case there was previously valid license which currently is expired.
The only drawback of being in state "Expired" is no support in case of any questions/problems.
The Scheduler 2.0 - Release Notes
New version of plugin brings more generic treatment of fields that user may define for particular project and issue type. You can create scheduled issue jobs and set values for all fields you are provided when you create new issue in the traditional manner. Even if you change field configuration after creating scheduled issue our plugin can still create new issue basing on scheduled job template.
New version is well fitted into Jira 4.4 user interface. As you can see on attached screenshot this version brings you more information on Issue Scheduler screen. In Issue Scheduler table additional columns was added - such as "Type", "Priority" and also "Reporter".
There is also ability to sort data by clicking on most any column (excluding Actions column).
Sort order is as intuitive as possible. For example clicking on "Name" column make the data sorted alphabetically - ascending or descending depending on column click state. To visualize asc, desc modes there is small narrow icon next to column name. By clicking on "Priority" column name user is able to sort data by priority sequence. "Fire Time" column sorting is defined as next fire time occurrence so if you click on it one time data will be sorted in first fire time at top order. Clicking on it ones again reverse the order - so last fired issue jobs at the top.
IMPORTANT NOTE for 1.5.x & 1.6.x plugin version users. Because of new functionality added, there is no way to upgrade plugin from version 1.5.x or 1.6.x to 2.0. Previous version must be completely removed (together with existing data).
Build 16 - release notes
TheScheduler 2.0 brings ability to backup and restore all scheduler data.
You can now import all previously exported scheduler data using common xml interchange format.
Moreover there are couple of fixes bundled with this version which make our plugin more predictable in situation when some information (like issue priorities) are missing.
Because our plugin is using its own database to store scheduled issue templates its very important to ensure consistency with Jira database.
2.0 version deal better with unexpected situation in which some information are missing.
This version includes fixes for:
TSP-38 - fixed problem with not suitable access rights when creating real issue basing on scheduled issue template.
When user is creating new scheduled issue template he has some access rights which give him ability to view/edit particular set of fields.
After template creation this situation may change and he is no longer able to view/edit some of the fields he was able before.
This fix brings ability to choose user which will be used as an real issue creator - this user must have all necessary privileges to create real issue.
TSP-41 - Fixed problem with ignored default values on custom fields after real issue creation.
Build 12 - release notes
This release includes fix for APDC-7. If for some reason real issue cannot be created based on scheduler issue job template then appropriate job entry is highlighted to allow user to distinguish the invalid scheduled job issues.
These are release notes for jira plugin - The Scheduler 1.6.1 compatible with Jira 4.4.
IMPORTANT NOTE for 1.5 plugin version users. Because of DB schema modifications (cause by new version of the Quartz library), there is no way to upgrade plugin from version 1.5 to 1.6.x. Previous version must be completely removed (together with existing data).
Release notes for build 15
Updated 1.6.1 version now contains backup functionality which allow user to export scheduler data to xml file.
This file can be then used as an input to any new TheScheduler version already released.
You can import this xml file using either 2.0 or 2.5 version of our plugin.
Release notes for build 11
Release notes for build 8
These are release notes for jira plugin - The Scheduler 1.6 compatible with Jira 4.3.
IMPORTANT NOTE for 1.5 plugin version users. Because of DB schema modifications (cause by new version of the Quartz library), there is no way to upgrade plugin from version 1.5 to 1.6. Previous version must be completely removed (together with existing data).
Release notes for build 14
Updated 1.6 version now contains backup functionality which allow user to export scheduler data to xml file.
This file can be then used as an input to any new TheScheduler version already released.
You can import this xml file using either 2.0 or 2.5 version of our plugin.
Release notes for build 10
Release notes for build 7
Release notes for build 3
Presented bug fixes and new functionality compared to version 1.5 of the plugin.
1) Fixed bug with displaying Due Date field (date picker/calendar)
Across the older version of Jira prior to 4.2 the resources required by calendar component as handled in different manner.
To make the Due Date (popup Calendar) component display proper it requires some new code in Java that is not backward compatible with Jira 4.1 and lower.
2) Fixed bug with displaying Priority field on the Create/Edit scheduled job form.
3) Making the Cron Expression field under the "Advenced" options tab auto fill it's content with the latest
proper expression while editing/updateing scheduled job.
4) Added new functionality to allow user to delete all or selected jobs by pressing one button.
5) Changing the way the "Do Not Duplicate" feature works.
Currently when this option is checked for particular scheduled job each event that will occure change
the priority of the existing issue (created before upon this scheduled job) to higher.
This behavior will take place each time until the current issue gets the highest possible priority
or is closed/resolved by user.
6) Adding feature that allow user to choose between static or dynamic due date when creating/updating scheduled job.
User may have preference to set up due date like "2 weeks and 4 days from evant time" so due date is considered dynamic
- as an offset from issue creation date.
7) Fixed bug with missing column in table definition for database schema which prevents the scheduled job being Created/Updated.
This issue occurred becouse Jira 4.3 uses diffrent version of Quartz library - 1.5.1 (not as previusly 1.4.5)
Quartz in a new version uses changed database schema.
These are release notes for jira plugin - The Scheduler 1.5.1
Presented bug fixes and new functionality compared to version 1.5 of the plugin.
IMPORTANT NOTE for 1.5 plugin version users. Because of functional improvements introduced, there is no way to upgrade plugin from version 1.5 to 1.5.1. Previous version must be completely removed (together with existing data).
Release notes for build 6
Release notes for build 2
1) Fixed bug with displaying Due Date field (date picker/calendar)
Across the older version of Jira prior to 4.2 the resources required by calendar component as handled in different manner.
To make the Due Date (popup Calendar) component display proper it requires some new code in Java that is not backward compatible with Jira 4.1 and lower.
2) Fixed bug with displaying Priority field on the Create/Edit scheduled job form.
3) Making the Cron Expression field under the "Advenced" options tab auto fill it's content with the latest
proper expression while editing/updateing scheduled job.
4) Added new functionality to allow user to delete all or selected jobs by pressing one button.
5) Changing the way the "Do Not Duplicate" feature works.
Currently when this option is checked for particular scheduled job each event that will occure change
the priority of the existing issue (created before upon this scheduled job) to higher.
This behavior will take place each time until the current issue gets the highest possible priority
or is closed/resolved by user.
6) Adding feature that allow user to choose between static or dynamic due date when creating/updating scheduled job.
User may have preference to set up due date like "2 weeks and 4 days from evant time" so due date is considered dynamic
- as an offset from issue creation date.