New features:

• new way of displaying assignee column in exports
• checkbox select all at Scheduled Issues table now is aware of filters
• handle more than 50 subtasks

Fixed bugs:

• minor migrations fixes
• minor UI fixes
• SI Wizard fixes

Remember about our: Status Page and Release Notes

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

• Performance - Scheduled Issue table performance improvement
• Minor UI/UX fixes and improvements

Bug fixing

• Migration - bug fixes
• Compatibility fixes - The Scheduler is now compatible with Advanced Roadmaps and Insight for Jira Service Management

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:

• Performance - Scheduled Issue table performance improvement
• Minor UI/UX fixes and improvements

Bug fixing:

• Migration - bug fixes
• Compatibility fixes - The Scheduler is now compatible with Advanced Roadmaps and Insight for Jira Service Management

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

• Migrations are now available again - this version includes migration fixes
• Issues created using the workflow trigger now have comments which Issue transition created that issue
• Minor UI/UX fixes and improvements
• Other 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.

Bug fixing

• Migrations are now available again - this version includes migration fixes
• Issues created using the workflow trigger now have comments which Issue transition created that issue
• Minor UI/UX fixes and improvements
• Other 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

• We changed “Create” button into “Create template” to emphasise that Scheduled Issues can be used without any triggers and work as Templates… more about it soon.
• SI table improvements: filter by triggers, persistent setting for number of displayed rows
• SI description in 1st step was limited to 1k chars to match our Cloud version limit
• Minor UI/UX improvements

Bug fixes

• Fixed issues related to migration and empty values
• Fixed display issues related to bulk operations
• Minor UI/UX 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

• We changed “Create” button into “Create template” to emphasise that Scheduled Issues can be used without any triggers and work as Templates… more about it soon.
• SI table improvements: filter by triggers, persistent setting for number of displayed rows
• SI description in 1st step was limited to 1k chars to match our Cloud version limit
• Minor UI/UX improvements

Bug fixes

• Fixed issues related to migration and empty values
• Fixed display issues related to bulk operations
• Minor UI/UX 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:

• Security related improvements
• 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:

• Security related improvements
• Minor bug fixes

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:

• fixed issue with user filtering in SI table
• 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 (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:

• fixed issue with user filtering in SI table
• 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 (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:

• Under the hood changes, preparing for migration to Jira Cloud, v6.5.0 will be the 1st migratable version
• Ability to bulk edit cloned Scheduled Issues - you can easily edit multiple SI of the same Issue type, right after cloning and e.g. change the target project
• Removing Access Manager
• Minor improvements

Bug Fixing:

• Fixed issue with security level of scheduled subtasks not being inherited from parent issue.
• Minor bug fixes

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:

• Under the hood changes, preparing for migration to Jira Cloud, v6.5.0 will be the 1st migratable version
• Ability to bulk edit cloned Scheduled Issues - you can easily edit multiple SI of the same Issue type, right after cloning and e.g. change the target project
• Removing Access Manager
• Minor improvements

Bug Fixing:

• Fixed issue with security level of scheduled subtasks not being inherited from parent issue.
• Minor bug fixes

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:

• Bulk subtasks removal - you can easily remove multiple subtask on the SI details page

Improvements:

• Fix button in SI table - allowing to move to SI edition faster
• Predefined variables in Epic Name
• Scheduled Issue name added in Execution History - we noticed it might hard to figure out, which issue was created from which template, this should help to identify correct templates
• SI Incomplete state will show more detailed information about the reasons
• Minor improvements

Bug Fixing:

• Fixed issue with installation v6.4.x on Jira < 8.0
• Fixed issue with wrong calendar week in predefined variables

Important: Our team has checked The Scheduler for log4j vulnerability - application is not affected.

New features:

• Bulk subtasks removal - you can easily remove multiple subtask on the SI details page

Improvements:

• Fix button in SI table - allowing to move to SI edition faster
• Predefined variables in Epic Name
• Scheduled Issue name added in Execution History - we noticed it might hard to figure out, which issue was created from which template, this should help to identify correct templates
• SI Incomplete state will show more detailed information about the reasons
• Minor improvements

Bug Fixing:

• Fixed issue with installation v6.4.x on Jira < 8.0
• Fixed issue with wrong calendar week in predefined variables

Important: Our team has checked The Scheduler for log4j vulnerability - application is not affected.

New feature

• Ability to change Creator in bulk edition - this is the answer to one of the common problems of SI creators leaving the organization, now you can easily change the creator in bulk. This feature is available to Jira Administrators and users with Administer Project permission. Tip: consider creating a dedicated “The Scheduler User” as creator and reporter to make sure those templates are robust and issue creation notifications are sent.

Improvements:

• Coning templates - Now, all app users can clone Scheduled Issues between projects, as long they have the correct permissions in target project. If there are missing fields or SI fails validation, it will be created as invalid and require manual fix.
• SI sharing: If selected 'Everyone' then other options are hidden
• On Import Page - improved message about already exist SI
• Compatibility updates:
  • for dynamic dates with custom date fields from Portfolio (Advanced Roadmaps)
  • for some operations in Checklist for Jira

Minor bug fixing

New feature

• Ability to change Creator in bulk edition - this is the answer to one of the common problems of SI creators leaving the organization, now you can easily change the creator in bulk. This feature is available to Jira Administrators and users with Administer Project permission. Tip: consider creating a dedicated “The Scheduler User” as creator and reporter to make sure those templates are robust and issue creation notifications are sent.

Improvements:

• Coning templates - Now, all app users can clone Scheduled Issues between projects, as long they have the correct permissions in target project. If there are missing fields or SI fails validation, it will be created as invalid and require manual fix.
• SI sharing: If selected 'Everyone' then other options are hidden
• On Import Page - improved message about already exist SI
• Compatibility updates:
  • for dynamic dates with custom date fields from Portfolio (Advanced Roadmaps)
  • for some operations in Checklist for Jira

Minor bug fixing

Improvements:

• We have added new predefined variables (available in Cloud version) - to see the full list visit: Predefined variables
• Minor UI/UX improvements

Bug fixing:

• Fixed issue with empty list of holidays under calendar after import and opening calendar
• Fixed issue with calendar date list is not updated for selected year
• Minor bug fixes

Improvements:

• We have added new predefined variables (available in Cloud version) - to see the full list visit: Predefined variables
• Minor UI/UX improvements

Bug fixing:

• Fixed issue with empty list of holidays under calendar after import and opening calendar
• Fixed issue with calendar date list is not updated for selected year
• Minor bug fixes

Improvements:

• More clear information in warnings related to permissions

Bug fixing:

• Fixed issue with validation of DateTimeField fields
• Fixed issue with incomplete projects list for Administrators on edit SI dialog, when “Creator” field is empty
• Fixed issue with migrations fails, when there is no group with “Jira Administrators” global permission
• Fixed issue with month written in French language when using “MMMM” format with combination of applied ISO8601 standard, English will be used
• Minor bug fixes

Improvements:

• More clear information in warnings related to permissions

Bug fixing:

• Fixed issue with validation of DateTimeField fields
• Fixed issue with incomplete projects list for Administrators on edit SI dialog, when “Creator” field is empty
• Fixed issue with migrations fails, when there is no group with “Jira Administrators” global permission
• Fixed issue with month written in French language when using “MMMM” format with combination of applied ISO8601 standard, English will be used
• Minor bug fixes

Improvements:

• Added option to choose prefix or suffix for Scheduled Issue name in bulk cloning
• Minor UI/UX improvements

Bug fixing:

• Fixed issue with permission "Anyone on the web" not working
• Fixed issue with Subtasks not getting Security Level field populated from parent issue
• Fixed issue with different timezone usage in Edit Triggers dialog
• Fixed issue with Calendar picker being empty in Edit Triggers dialog
• Minor 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

Improvements:

• Added option to choose prefix or suffix for Scheduled Issue name in bulk cloning
• Minor UI/UX improvements

Bug fixing:

• Fixed issue with permission "Anyone on the web" not working
• Fixed issue with Subtasks not getting Security Level field populated from parent issue
• Fixed issue with different timezone usage in Edit Triggers dialog
• Fixed issue with Calendar picker being empty in Edit Triggers dialog
• Minor 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:

• Global permission: The Scheduler: Access
• Project permission: The Scheduler: Use

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

• Last execution status in Scheduled Issues table - with this little feature, you can easily see the result of the last execution - it will help you to spot any failures or incomplete executions, make sure to add it to your visible columns
• Scheduled Issues table was completely rebuild
• We’ve improved some of the warning messages
• Little UI/UX tweaks here and there

Bug fixes:

• Fixed issues with SI access sharing
• Minor 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:

• Global permission: The Scheduler: Access
• Project permission: The Scheduler: Use

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

• Last execution status in Scheduled Issues table - with this little feature, you can easily see the result of the last execution - it will help you to spot any failures or incomplete executions, make sure to add it to your visible columns
• Scheduled Issues table was completely rebuild
• We’ve improved some of the warning messages
• Little UI/UX tweaks here and there

Bug fixes:

• Fixed issues with SI access sharing
• Minor 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:

• Compatibility with Smart Issue Templates plugin
• Problem with properly displaying and using by The Scheduler the "Use ISO8601 standard in Date Picker" option from “Look and Feel” Jira setting
• Visual View in Summary and Description fields on Scheduled Issue Details Page
• Minor 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:

• Compatibility with Smart Issue Templates plugin
• Problem with properly displaying and using by The Scheduler the "Use ISO8601 standard in Date Picker" option from “Look and Feel” Jira setting
• Visual View in Summary and Description fields on Scheduled Issue Details Page
• Minor 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:

• Compatibility issues with ScriptRunner, we had to remove app related fields validation to unlock the usage of both apps. Make sure you are using correct values

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:

• Compatibility issues with ScriptRunner, we had to remove app related fields validation to unlock the usage of both apps. Make sure you are using correct values

Improvement:

• “Incomplete” status is now available as execution result in the “Failed Executions History” - Jira Administrators can monitor all failed and incomplete executions in 1 place

Bug Fixing:

• Cases related to removed workflow statuses which should result in “Incomplete” status
• Minor 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:

• “Incomplete” status is now available as execution result in the “Failed Executions History” - Jira Administrators can monitor all failed and incomplete executions in 1 place

Bug Fixing:

• Cases related to removed workflow statuses which should result in “Incomplete” status
• Minor 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:

• New link to predefined variables, comparing Server (& Data Center) and Cloud
• “Get started” page, to allow quick start and grasp the app usage ideas, with useful links
• Minor UI/UX improvements

Bug fixing:

• Removed outdated resources definitions, spamming logs
• Anonymization of users used in app only
• Issue with cloning SI
• Bulk edition checkboxes
• Missing styles on Jira 8.13.x and 8.14.x
• Minor bug fixes

Improvements:

• New link to predefined variables, comparing Server (& Data Center) and Cloud
• “Get started” page, to allow quick start and grasp the app usage ideas, with useful links
• Minor UI/UX improvements

Bug fixing:

• Removed outdated resources definitions, spamming logs
• Anonymization of users used in app only
• Issue with cloning SI
• Bulk edition checkboxes
• Missing styles on Jira 8.13.x and 8.14.x
• Minor bug fixes

Bug fixing:

• Error on plugin startup on some of Jira versions lower than 8.0.0
• Error with exporting Scheduled Issues related to Microsoft SQL Server database
• Small dependency improvements

Bug fixing:

• Error on plugin startup on some of Jira versions lower than 8.0.0
• Error with exporting Scheduled Issues related to Microsoft SQL Server database
• Small dependency improvements

Improvements:

• Major UI/UX improvements on Scheduled Issue Details page
• Stability improvements
• Scheduled Issues export minor improvements
• Technical improvements under the hood
• Prevent caching on plugin update
• Minor UI/UX & Jira 8.12.0 compatibility improvements

Minor bug fixing:

• Dropdowns on Create/Edit Scheduled Issue page
• Modified by field taking the value of creator
• Importing SI with shared user

Improvements:

• Major UI/UX improvements on Scheduled Issue Details page
• Stability improvements
• Scheduled Issues export minor improvements
• Technical improvements under the hood
• Prevent caching on plugin update
• Minor UI/UX & Jira 8.12.0 compatibility improvements

Minor bug fixing:

• Dropdowns on Create/Edit Scheduled Issue page
• Modified by field taking the value of creator
• Importing SI with shared user

Improvements

• Add current user in multi-user pickers - new manual execution feature, if in some field there are users A, B, C - this feature adds current user, making it more diverse for templating
• Indications of manual executions for User Fields types - with look at the SI table you will notice, which scheduled issues will be changed on manual executions. SI are also marked in details view and in manual execution dialog
• Creating SI from existing Jira issue - default name of SI will reference source issue key and timestamp, when it was created
• Minor UI/Ux improvements

Minor bug fixing

• Editing scheduled issue subtask - fixed error related to wrong link redirection, resulting in some users not being able to edit subtasks
• Default field values on fields not used on create issue screen - fields are now being correctly set with predefined defaults
• Refreshing user avatars - in "Copy from parent" feature dedicated for subtasks
• Minor bug fixes with displayed results in upcoming executions

Improvements

• Add current user in multi-user pickers - new manual execution feature, if in some field there are users A, B, C - this feature adds current user, making it more diverse for templating
• Indications of manual executions for User Fields types - with look at the SI table you will notice, which scheduled issues will be changed on manual executions. SI are also marked in details view and in manual execution dialog
• Creating SI from existing Jira issue - default name of SI will reference source issue key and timestamp, when it was created
• Minor UI/Ux improvements

Minor bug fixing

• Editing scheduled issue subtask - fixed error related to wrong link redirection, resulting in some users not being able to edit subtasks
• Default field values on fields not used on create issue screen - fields are now being correctly set with predefined defaults
• Refreshing user avatars - in "Copy from parent" feature dedicated for subtasks
• Minor bug fixes with displayed results in upcoming executions

New features

• Default share settings - each newly created SI will have sharing set based on your settings
• Default visible columns - in project settings you can set visible columns in table with SI, so that users can see desired column by default, each user can adjust it to their own needs
• Due Date fields support - we have added due date field to the SI table and to SI details page
• Manual Execution features - allows to set any user picker into the user who manually triggered creation of issue. This way any user picker (eg Assignee) can be set to different user
• Set status on issue creation - now you can change the status in which issue will be created. If you use kanban boards, this will save you lots of nerves
• Copy from Parent - set the subtasks Assignee as the value from its parent issue

Improvements

• Edit triggers - without going through whole wizard. Access it from SI table actions column, SI details page: in more option and under triggers table
• Minor UI/UX and performance improvements

New features

• Default share settings - each newly created SI will have sharing set based on your settings
• Default visible columns - in project settings you can set visible columns in table with SI, so that users can see desired column by default, each user can adjust it to their own needs
• Due Date fields support - we have added due date field to the SI table and to SI details page
• Manual Execution features - allows to set any user picker into the user who manually triggered creation of issue. This way any user picker (eg Assignee) can be set to different user
• Set status on issue creation - now you can change the status in which issue will be created. If you use kanban boards, this will save you lots of nerves
• Copy from Parent - set the subtasks Assignee as the value from its parent issue

Improvements

• Edit triggers - without going through whole wizard. Access it from SI table actions column, SI details page: in more option and under triggers table
• Minor UI/UX and performance improvements

New bulk operations: Enable / Disable Scheduled Issues - now you can deactivate issues in bulk

Improvements:

• Performance improvements related to large numbers of scheduled issues in manage add-ons section
• Transfer ownership compatibility (available in Jira > 8.7.0) - you can easily transfer all Scheduled Issues from user being deactivated to someone else - to keep it operational
• Technical improvements under the hood
• Minor UI/UX improvements

Minor bug fixing

• Missing description in cloning SI dialog in details page
• Fixed error in logs
• Missing indication of next execution being skipped in issue panel
• Missing link to JQL in history accessed from scheduled issue details page
• Fixed order of upcoming executions

New bulk operations: Enable / Disable Scheduled Issues - now you can deactivate issues in bulk

Improvements:

• Performance improvements related to large numbers of scheduled issues in manage add-ons section
• Transfer ownership compatibility (available in Jira > 8.7.0) - you can easily transfer all Scheduled Issues from user being deactivated to someone else - to keep it operational
• Technical improvements under the hood
• Minor UI/UX improvements

Minor bug fixing

• Missing description in cloning SI dialog in details page
• Fixed error in logs
• Missing indication of next execution being skipped in issue panel
• Missing link to JQL in history accessed from scheduled issue details page
• Fixed order of upcoming executions

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:

• Project Administrators can share SI in project as Jira Administrators
• Clone prefix is pulled from Jira global settings
• More details in performance warning
• Under the hood technical updates
• Minor UI/UX improvements

Bug Fixes:

• Issues with action available on Scheduled Issue details page
• Minor 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:

• Project Administrators can share SI in project as Jira Administrators
• Clone prefix is pulled from Jira global settings
• More details in performance warning
• Under the hood technical updates
• Minor UI/UX improvements

Bug Fixes:

• Issues with action available on Scheduled Issue details page
• Minor bug fixes

Compatibility update with Jira 8.7.x

Improvements:

• Ability to set Scheduled Issue creator in 1st step of creation of Scheduled Issue (for Administer Projects permission)
• Extend default Sharing of Scheduled Issues to project permission Administer Projects
• Ability to set limit on number of results in FEH page
• Minor UI/UX improvements

Bug fixes

• Fixed issue with calendars being blocked from editing
• Compatibility with Power Database Fields PRO
• Minor bug fixes

Improvements:

• Ability to set Scheduled Issue creator in 1st step of creation of Scheduled Issue (for Administer Projects permission)
• Extend default Sharing of Scheduled Issues to project permission Administer Projects
• Ability to set limit on number of results in FEH page
• Minor UI/UX improvements

Bug fixes

• Fixed issue with calendars being blocked from editing
• Compatibility with Power Database Fields PRO
• Minor bug fixes

New features:

• Import calendars from .ics file - with few clicks, you can import calendars eg. with national holidays and adjust it to your needs

Improvements:

• We lowered permission required to clone Scheduled Issues between projects - now Administer Projects permission is checked
• Users with Administer Project permission are granted the right to change creator of Scheduled Issues - to decrease Jira Administrators overhead
• More option for bulk cloning: "Add prefix" or "replace all" for description field
• “Last clean” as a new option for limiting displayed results on Failed Executions History page
• Minor UI/UX improvements

Bug fixes:

• Blocked possibility to add epic link in subtask in Scheduled Issue
• Minor bug fixing

New features:

• Import calendars from .ics file - with few clicks, you can import calendars eg. with national holidays and adjust it to your needs

Improvements:

• We lowered permission required to clone Scheduled Issues between projects - now Administer Projects permission is checked
• Users with Administer Project permission are granted the right to change creator of Scheduled Issues - to decrease Jira Administrators overhead
• More option for bulk cloning: "Add prefix" or "replace all" for description field
• “Last clean” as a new option for limiting displayed results on Failed Executions History page
• Minor UI/UX improvements

Bug fixes:

• Blocked possibility to add epic link in subtask in Scheduled Issue
• Minor bug fixing

New features

• Failed Executions History - page dedicated to troubleshooting of not created issues
• Bulk cloning - now you can clone multiple SIs, it allows to move them from project A to project B !
• Redirection to JQL from Execution History - easily see all created issues as a JQL results

Improvements:

• More precise percentage statistics - 2 decimals
• Closing of message box in statistics
• Modified Scheduler’s JQL function schedulerGetGeneratedIssuesByName(““) - accepts only SI names (used to accept also project ID) in JQL you can use it with combination of project for more precise results
• Improved exception logging

Bug fixes:

• Minor issues related to increase priority feature
• Minor issues with statistics

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

• Failed Executions History - page dedicated to troubleshooting of not created issues
• Bulk cloning - now you can clone multiple SIs, it allows to move them from project A to project B !
• Redirection to JQL from Execution History - easily see all created issues as a JQL results

Improvements:

• More precise percentage statistics - 2 decimals
• Closing of message box in statistics
• Modified Scheduler’s JQL function schedulerGetGeneratedIssuesByName(““) - accepts only SI names (used to accept also project ID) in JQL you can use it with combination of project for more precise results
• Improved exception logging

Bug fixes:

• Minor issues related to increase priority feature
• Minor issues with statistics

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:

• on statistics page (styling, sorting)
• in project settings
• in execution history

Minor bugfixes

Minor UI/UX Improvements:

• on statistics page (styling, sorting)
• in project settings
• in execution history

Minor bugfixes

Improvements:

• Results of 'show all created issues' and 'show upcoming issues' dependable on selection from the table, allowing to export more relative results
• Created subtasks, with statuses, displayed in execution history
• Redirection to newly created calendar
• More details in statistics - you can see the contribution of app in all projects, also quickly navigate to Scheduled Issues in project or the results of JQL query

Bug fixing:

• Issue with editing scheduled issue (corner case with same username as other user’s userkey)
• Minor bug fixing

Improvements:

• Results of 'show all created issues' and 'show upcoming issues' dependable on selection from the table, allowing to export more relative results
• Created subtasks, with statuses, displayed in execution history
• Redirection to newly created calendar
• More details in statistics - you can see the contribution of app in all projects, also quickly navigate to Scheduled Issues in project or the results of JQL query

Bug fixing:

• Issue with editing scheduled issue (corner case with same username as other user’s userkey)
• Minor bug fixing

Version 6.1 is finally here.

New features:

• Global Settings page - manage some of the settings from Jira Administrator level instead of Project level
• JQL functions - search for issues created by The Scheduler
• Export upcoming executions to CSV - you can export key data of future issues e.g. for audit purpose

Improvements:

• We have added issue status in execution history - now you can see how things are going
• Details about which issue transition triggered creation of other issue
• New setting related to calendars and workflow transitions
• Set start / end date for workflow triggers
• More control over displaying past / future issues (by amount and date)
• Minor UI/UX improvements

Bug fixing:

• Issues with long interval triggers
• Scheduling existing issue with missing values in cascading select field type
• Bulk edit option do not update "modified at" column
• Error on viewing Scheduled Issue table
• Errors in logs after update to v6.1.0
• Minor bug fixes

Version 6.1 is finally here.

New features:

• Global Settings page - manage some of the settings from Jira Administrator level instead of Project level
• JQL functions - search for issues created by The Scheduler
• Export upcoming executions to CSV - you can export key data of future issues e.g. for audit purpose

Improvements:

• We have added issue status in execution history - now you can see how things are going
• Details about which issue transition triggered creation of other issue
• New setting related to calendars and workflow transitions
• Set start / end date for workflow triggers
• More control over displaying past / future issues (by amount and date)
• Minor UI/UX improvements

Bug fixing:

• Issues with long interval triggers
• Scheduling existing issue with missing values in cascading select field type
• Bulk edit option do not update "modified at" column
• Error on viewing Scheduled Issue table
• Errors in logs after update to v6.1.0
• Minor bug fixes

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:

• Major feature of this release is to provide full Jira 8 compatibility for our Application - The Scheduler

Improvements:

• Fixed issue with export feature.

Improvements:

• Added project setting for enabling execution of workflow triggers in calendar
• Minor bug-fixes

Improvements:

• Enhanced support for MS SQL database connection handling for statistics module

Improvements:

• Fixed error occurring when trying to schedule an issue from an existing one in Jira
• Fixed error on reading workflow triggers

New features:

• New trigger type "workflow" - execute Scheduled Issues on workflow transitions
• Add Scheduled Issues to active sprint

Improvements:

• "What's New" section - here you can learn about new features with direct links to documentation

• Fix of XML external entity vulnerability
• Added compatibility with 3rd party custom fields
• Linking to proper epics when executing the triggers
• Improved performance
• Minor bug fixing

New features:

• Calendars - Global and Project, now you can include holidays and days off when task shouldn't be created
• Monthly and Yearly triggers - new types of triggers allow you to easily scheduled tasks recurring every 'x' month or years

Improvements:

• Execute selected - you can easily check all task and execute them all at once
• Detailed upcoming execution preview - at 3rd step you can preview multiple triggers to preview the schedule

Use our dedicated Customer Portal to report bugs and request new features.

Bug fixing:

• Issues with Scheduled Issues without priority field
• Issue #281
• Issue #292
• Issue #302
• Issue #300

New features:

• Scheduled Issue - info box - piece of information on issue details page. Now you can see if particular issue was created by The Scheduler! You can also preview its next occurrence (also navigate to original SI - if you have access to it). You can turn this feature on/off within project settings.
• Filtering by columns - huge improvement on searching/filtering possibilities within Scheduled Issues table.
• Trigger execution preview - Upcoming execution preview at 3rd step of the wizard, now you can easily adjust trigger settings and preview future execution dates before saving scheduled issue (works with multiple triggers).

Bug fixing:

• Issue #292
• Issue #296
• Issues involving JIRA System Administrators / JIRA Administrators
• Minor bug fixes

Improvements:

• Information about sub-tasks on table view – added to SI name
• Displaying number of scheduled Issues
• Minor UI/UX improvements

Bug fixing:

• Issue #249 - Incorrect timezone in date display
• Issue #269 - Scheduled Issues not being shown, Errors in JIRA Log file
• Missing tooltips for invalid issues
• Linking options matching outgoing link names
• Message box about "visibility" of Scheduled Issues can be closed :)

Exciting Version 5.1.0 !

New Features:

• Interval triggers - long time awaited - now you can create issues every 2 weeks or 3 days etc.
• Run once trigger - scheduled issue will expire after creating 1 planned issue.
• The Scheduler Settings - in project settings section - you can turn on/off visibility for non shared scheduled issues for other users.

Bug fixing:

• Issue with custom date.time fields not saving correct hours.
• Minor 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:

• Issue #242 - fixed default option for "once per day" trigger
• Issue #241, #235 - loading add-ons page "Manage Scheduled Issues"
• Fixed issue with blocked Access for Project Lead

Fixed issues:

• Issues #238, #239 - related to change in permissions, non-administrator users could not create / edit Scheduled Issues
• Removed irrelevant announcement message visible for administrators in Jira 7.4.3
• #233 - Linking issues
• #205 - Optimized logging

Improvements:

• Removed unnecessary information box displayed along create / edit Scheduled Issue wizard
• Minor UI 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.

• If you change Creator you would see only Project in which this person can create issues.
• If you remove Creator you will see all available Projects - when you chose one then you can pick appropriate Creator (as this field updates).
• This fixes issues with editing Service Desk Scheduled Issues with missing Issue Types due to lack of permission to create issues in this projects.

Fixed issues:

• #223, #228, #229 - redirection after creating / editing Scheduled Issue
• #224 - order of sub-tasks in cloned Scheduled Issue

• Security fix of XSS vulnerability
• Minor fixes of Scheduled Sub-tasks creation
• Fixed editing "Invalid" Scheduled Issues without creator
• Fixed redirection after creating scheduled issue

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.

• Fixed Issue #193
• Fixed Issue #194

• Fixed an issue with certain Data Center deployments
• Minor bug fixes

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:

• Sub-tasks - it's a game changer - now you can easily create Scheduled Issues with attached sub tasks, even more ... you can transform your already existing issues into Scheduled Issues and your sub-tasks will be automatically included
• Detailed view - we have added special page allowing you to preview your scheduled tasks in different than table view - now you can focus on task and planning it's sub-task. In the bottom tabs there is quick preview of triggers, last 5 executions and upcoming 5 executions
• Easily spot manually fired tasks - little "M" next to fire date indicates this issue was executed manually
• UI improvements

For more details please refer to documentation or contact us using one off available channels

We are open for feedback and ideas!

• Fix cloning issues that occurred on MSSQL
• Security fix of XSS vulnerability

• Fixed Issue #175
• Fixed Issue #176

• Fixed issue with Import/Export functionality
• Drastically improved loading time of Scheduled Issues table

• Fixed Issue #159
• Fixed Issue #161
• Fixed Issue #143

• Fixed Issue #153

• Support for Jira 7.2
• Internationalized all the labels so that they can be translated
• Fixed issue #139
• Numerous UI improvements

• It is now possible to schedule creating subtasks to the existing issue in Jira (more advanced subtasks support coming soon in 4.3!)
• Added filtering option to "Show Created Issues"/"Show Upcoming Executions" dialogs
• Fixed bug with adding/deleting triggers in Scheduled Issue on Jira < 7.1 version
• Fixed Creator avatar on the Edit Scheduled Issue page
• Lot of other smaller UI fixes and improvements.

• Added column with shared users for each Scheduled Issue,
• Added dialogs with history of created issues and future Scheduled Issue executions for each Scheduled Issue or Project,
• Lot of other smaller UI fixes and improvements.

• Fixed ClassCastException #126
• Fixed inaccurate calculation of next fire time date

• Much requested "Next Fire Time" feature is back (Issues #118, #123)
• Improved Bulk Editing
• Setting dates in custom fields (Issue #76)
• Sorting date-based columns chronologically (Issue #75)

Jira 7.1.0 is now supported!

New features:

• Added ${fireCount} variable that can be used to parametrize your scheduled issues even further
• Issue #115: Made it possible to format createdDate and dueDate fields using Joda Time date formats. For example, you can format createdDate field as follows: ${createdDate.format("dd/MM/yyyy")}

Bugfixes:

• Issue #106
• Issue #111
• Issue #120

4.0.6:

• Fixed a critical issue that prevented the users running Jira on MS SQL from upgrading to TheScheduler to 4.0.5.

• Added mass share feature
• Allow to link recurring issues
• Reorganization of navigation on Jira admin site

4.0.4:

• Fixed bug related to Assignee field,
• Fixed bug related to Scheduled Job with more than one trigger
• Added a new variable to the summary fields in description - numerically month

4.0.3:

• Fixed bug related to importing one project,
• Fixed bug related to forgetting the creator after import SI,
• Remove the "Next Fire Time" from scheduled issue table and Due date Field

4.0.2:

• Fixed "Due Date" field error
• Fixed saving of tables columns layout configuration

4.0.1:

• Fix of SI initialization (starting old SI after Scheduler upgrade)

4.0.0:

• Added compatibility with Jira 7.0

• Fix of XML external entity vulnerability

• Fix cloning issues that occurred on MSSQL
• Security fix of XSS vulnerability

• Fixed Issue #194

• Scheduler will now remember your column setup on Scheduled Issues table
• Fixed old data format import issue

• Fix Issue #168

• Internationalized all the labels so that they can be translated
• Fixed German language bug
• Minor bugfixing

The Scheduler for Jira 6.x is back in Atlassian Marketplace!

New features:

• Scheduled issues bulk share

• Fix of error associated with the HSQL database.
• Added permission manager for The Scheduler

The Scheduler now supports a Clustered Jira Environment.

Added validation of Issue Security Field

• Added new import/export functionality of Scheduled jobs
• Added information in logs in case of issue creation failure

• fixed the issues with filter search
• fixed the issue where a creator could not be successfully updated

• fixed the issue with automatic clone scheduling
• fixed the issue where an user was not able to bulk edit issues anymore

NEW FEATURES

• Reinvented section for administrators (available under the Projects Administration section)
• Invented new feature that allows user to bulk edit Scheduled Issues

IMPROVEMENTS

• Ability to modify the Creator field when editing Scheduled Issue

NEW FEATURES

• invented new feature that allows user to clone an existing Scheduled Issue in scope of its project

IMPROVEMENTS

• the filter feature invented in 3.0.7 is case insensitive now

BUG FIXES

• fixed an issue where a Scheduled Issue state was not automatically refreshed when enabling/disabling a Scheduled Issue

NEW FEATURES

• invented new feature that allows user to filter Scheduled Issues

• invented new feature that allows user to change amount of displayed rows when viewing Scheduled Issues

PERFORMANCE IMPROVEMENTS

• improved performance when displaying the Scheduled Issues table that contains big amount of items
• improved performance when deleting Scheduled Issues, especially when deleting big amount of them

OTHER IMPROVEMENTS

• the Scheduled Issues table view has been improved so that having big amount of columns is more comfortable
• several minor improvements and adjustments

BUG FIXES

• fixed an issue where the button 'Back' was not working correctly when displaying information about expired or not existing license
• fixed an issue where the Due Date wrapper was causing unexpected exceptions after job has been fired
• fixed an issue where the resolution 'Done' was not recognized when using the 'Increase priority' feature

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

• TSP-35 and TSP-36 fixed
• The repairs the problem with not creatable/editable scheduled issues. 

Release notes for build 8

• Plugin layout aligned with Jira 4.4

These are release notes for jira plugin - The Scheduler 1.6 compatible with Jira 4.3.