Minor version update
Version history
CloudJira Cloud2023-03-12Minor version update 3.13.12Jira Data Center 7.2.0 - 9.11.12023-09-27Jira 9.11 compatibility and improvement Jira 9.11 compatibility.
Improvement:
- Show repeating issues panel when issue is not editable (it is when workflow status has jira.issue.editable=false property)
3.13.12Jira Server 7.2.0 - 9.11.12023-09-27Jira 9.11 compatibility and improvement Jira 9.11 compatibility.
Improvement:
- Show repeating issues panel when issue is not editable (it is when workflow status has jira.issue.editable=false property)
3.13.11Jira Data Center 7.2.0 - 9.10.22023-07-27Jira 9.10 compatibility Jira 9.10 compatibility
3.13.11Jira Server 7.2.0 - 9.10.22023-07-27Jira 9.10 compatibility Jira 9.10 compatibility
3.13.10Jira Data Center 7.2.0 - 9.9.22023-06-16Jira 9.9 compatibility Jira 9.9 compatibility
3.13.10Jira Server 7.2.0 - 9.9.22023-06-16Jira 9.9 compatibility Jira 9.9 compatibility
3.13.9Jira Data Center 7.2.0 - 9.8.22023-05-22Cloud migration bug fix Fixed a bug that causing migration to fail when Jira Server instance use non UTF-8 encoding.
3.13.9Jira Server 7.2.0 - 9.8.22023-05-22Cloud migration bug fix Fixed a bug that causing migration to fail when Jira Server instance use non UTF-8 encoding.
3.13.8Jira Data Center 7.2.0 - 9.8.22023-05-08Jira 9.8 compatibility Jira 9.8 compatibility
3.13.8Jira Server 7.2.0 - 9.8.22023-05-08Jira 9.8 compatibility Jira 9.8 compatibility
3.13.7Jira Data Center 7.2.0 - 9.7.22023-03-30Jira 9.7 compatibility Jira 9.7 compatibility
3.13.7Jira Server 7.2.0 - 9.7.22023-03-30Jira 9.7 compatibility Jira 9.7 compatibility
3.13.6Jira Data Center 7.2.0 - 9.6.02023-03-10Cloud migration bug fix Fixed a bug that causing none issues are migrated to cloud when project key is like a word from JQL syntax, e.g. "IN"
3.13.6Jira Server 7.2.0 - 9.6.02023-03-10Cloud migration bug fix Fixed a bug that causing none issues are migrated to cloud when project key is like a word from JQL syntax, e.g. "IN"
3.13.5Jira Data Center 7.2.0 - 9.6.02023-02-13Jira 9.6 compatibility and fix Jira 9.6 compatibility.
Fix:
- Solve a problem when Deutsch language is set and user can't edit details of the repeating due to validation error for recurrence end date
3.13.5Jira Server 7.2.0 - 9.6.02023-02-13Jira 9.6 compatibility and fix Jira 9.6 compatibility.
Fix:
- Solve a problem when Deutsch language is set and user can't edit details of the repeating due to validation error for recurrence end date
3.13.4Jira Data Center 7.2.0 - 9.5.12022-12-08Jira 9.5 compatibility Jira 9.5 compatibility
3.13.4Jira Server 7.2.0 - 9.5.12022-12-08Jira 9.5 compatibility Jira 9.5 compatibility
3.13.3Jira Data Center 7.2.0 - 9.4.102022-11-23Jira 9.4 compatibility, migration fixes Improvements
- Jira 9.4 compatibility
Bug fixes
- Fix a bug where migration to cloud process may ends as incomplete
3.13.3Jira Server 7.2.0 - 9.4.102022-11-23Jira 9.4 compatibility, migration fixes Improvements
- Jira 9.4 compatibility
Bug fixes
- Fix a bug where migration to cloud process may ends as incomplete
3.13.1Jira Data Center 7.2.0 - 9.3.32022-10-10Jira 9.3 compatibility, updates and fixes Improvements
- Jira 9.3 compatibility
- Show user display name instead of user key in administration view
Bug fixes
- Fixed a bug that did not allow to set "unassigned" value for assignee in the repeating configuration
- Fixed a bug in cloud migration causing that custom field id used in velocity expression has not been mapped to new id in cloud
3.13.1Jira Server 7.2.0 - 9.3.32022-10-10Jira 9.3 compatibility, updates and fixes Improvements
- Jira 9.3 compatibility
- Show user display name instead of user key in administration view
Bug fixes
- Fixed a bug that did not allow to set "unassigned" value for assignee in the repeating configuration
- Fixed a bug in cloud migration causing that custom field id used in velocity expression has not been mapped to new id in cloud
3.13.0Jira Data Center 7.2.0 - 9.2.12022-09-06Jira 9.2 compatibility, migration updates and fixes Improvements
- Support for new data in cloud migration (general settings, create subtask settings)
Bug fixes
- Fixed a bug that may cause that the end date of the recurrence may be migrated wrong
- Fixed a bug for the end date of the recurrence which is now set with the end of the day time to prevent the last possible occurrence from being missed
3.13.0Jira Server 7.2.0 - 9.2.12022-09-06Jira 9.2 compatibility, migration updates and fixes Improvements
- Support for new data in cloud migration (general settings, create subtask settings)
Bug fixes
- Fixed a bug that may cause that the end date of the recurrence may be migrated wrong
- Fixed a bug for the end date of the recurrence which is now set with the end of the day time to prevent the last possible occurrence from being missed
3.12.1Jira Data Center 7.2.0 - 9.1.12022-08-12Cloud migration bug fix Cloud migration bug fix
3.12.1Jira Server 7.2.0 - 9.1.12022-08-12Cloud migration bug fix Cloud migration bug fix
3.12.0Jira Data Center 7.2.0 - 9.1.12022-07-27Features, improvements and Jira 9.1 compatibility Feature
- The administrator can define default summary field value for create subtask and clone issue actions. [more...]
- The administrator can restrict the actions that can be set when configuring the repeat details. [more...]
Improvement
- New date object modifiers to set exact day, month and year in velocity expression
Bug fix
- Fixed a bug that lead to empty list of the repeatings on administration view when duplicated jobs are scheduled
- Fixed an issue where the value of the component field (for the create subtask action) was not saved when multiple values were selected
- Fixed a bug that caused the "next occurrence" custom field to be unnecessarily copied to target issues when performing an action
3.12.0Jira Server 7.2.0 - 9.1.12022-07-27Features, improvements and Jira 9.1 compatibility Feature
- The administrator can define default summary field value for create subtask and clone issue actions. [more...]
- The administrator can restrict the actions that can be set when configuring the repeat details. [more...]
Improvement
- New date object modifiers to set exact day, month and year in velocity expression
Bug fix
- Fixed a bug that lead to empty list of the repeatings on administration view when duplicated jobs are scheduled
- Fixed an issue where the value of the component field (for the create subtask action) was not saved when multiple values were selected
- Fixed a bug that caused the "next occurrence" custom field to be unnecessarily copied to target issues when performing an action
3.11.0Jira Data Center 7.2.0 - 9.0.02022-07-05Jira 9 compatibility Jira 9 compatibility
3.11.0Jira Server 7.2.0 - 9.0.02022-07-05Jira 9 compatibility Jira 9 compatibility
3.10.0Jira Data Center 7.2.0 - 8.22.62022-06-09Support for migration to Jira Cloud Features:
- Support for migration to Jira Cloud (more...)
- Ability to search issues with repeating by its owner in JQL: codedoers.repeating.owner = anyuserkey
3.10.0Jira Server 7.2.0 - 8.22.62022-06-09Support for migration to Jira Cloud Features:
- Support for migration to Jira Cloud (more...)
- Ability to search issues with repeating by its owner in JQL: codedoers.repeating.owner = anyuserkey
3.9.13Jira Data Center 7.2.0 - 8.22.62022-03-03Jira 8.22 compatibility and improvements Added Jira 8.22 compatibility.
Improvements:
- Ability to clear the value of a issue fields when cloning the source issue by leaving the input empty in the form
Bug fix:
- Resolved the problem when the issue can't be cloned when time tracking format is set to other than "pretty" and the Jira/user language uses other abbreviation for hour than "h" (e.g. Polish, Danish, Italian...). Fix relates to error message saying that timetracking_originalestimate has not valid value.
3.9.13Jira Server 7.2.0 - 8.22.62022-03-03Jira 8.22 compatibility and improvements Added Jira 8.22 compatibility.
Improvements:
- Ability to clear the value of a issue fields when cloning the source issue by leaving the input empty in the form
Bug fix:
- Resolved the problem when the issue can't be cloned when time tracking format is set to other than "pretty" and the Jira/user language uses other abbreviation for hour than "h" (e.g. Polish, Danish, Italian...). Fix relates to error message saying that timetracking_originalestimate has not valid value.
3.9.12Jira Data Center 7.2.0 - 8.21.12021-12-15Jira 8.21 compatibility Jira 8.21 compatibility
3.9.12Jira Server 7.2.0 - 8.21.12021-12-15Jira 8.21 compatibility Jira 8.21 compatibility
3.9.11Jira Data Center 7.2.0 - 8.20.262021-10-21Jira 8.20 compatibility Jira 8.20 compatibility
3.9.11Jira Server 7.2.0 - 8.20.262021-10-21Jira 8.20 compatibility Jira 8.20 compatibility
3.9.10Jira Data Center 7.2.0 - 8.19.12021-09-22Bug fix Bug fix
- Fixed a bug where an email notifications from the app have invalid content, like: "Could not locate resource com/codedoers/jira/recurringissues/templates/email...".
3.9.10Jira Server 7.2.0 - 8.19.12021-09-22Bug fix Bug fix
- Fixed a bug where an email notifications from the app have invalid content, like: "Could not locate resource com/codedoers/jira/recurringissues/templates/email...".
3.9.9Jira Data Center 7.2.0 - 8.19.12021-09-03Jira 8.19.0 compatibility and bug fix Bug fix
- Fixed a bug where Workflow Transition action is failing because of condition checks on issue field value. Previously issue fields has been updated after validation (what may cause the validation to fail), now it is done before validation.
3.9.9Jira Server 7.2.0 - 8.19.12021-09-03Jira 8.19.0 compatibility and bug fix Bug fix
- Fixed a bug where Workflow Transition action is failing because of condition checks on issue field value. Previously issue fields has been updated after validation (what may cause the validation to fail), now it is done before validation.
3.9.8Jira Data Center 7.2.0 - 8.18.22021-07-22Jira 8.18.1 compatibility Added compatibility for Jira 8.18.1
3.9.8Jira Server 7.2.0 - 8.18.22021-07-22Jira 8.18.1 compatibility Added compatibility for Jira 8.18.1
3.9.7Jira Data Center 7.2.0 - 8.17.12021-05-31Jira 8.17 compatibility and bug fix Added compatibility for Jira 8.17
Bug fix:
- Resolved a bug where project administrators are not able to edit project automation rules
3.9.7Jira Server 7.2.0 - 8.17.12021-05-31Jira 8.17 compatibility and bug fix Added compatibility for Jira 8.17
Bug fix:
- Resolved a bug where project administrators are not able to edit project automation rules
3.9.6Jira Data Center 7.2.0 - 8.16.12021-03-29Jira 8.16 compatibility Jira 8.16 compatibility
3.9.6Jira Server 7.2.0 - 8.16.12021-03-29Jira 8.16 compatibility Jira 8.16 compatibility
3.9.5Jira Data Center 7.2.0 - 8.15.12021-02-22Bug fix Bug fix
- Fixed a bug that prevented users from viewing the project automation page for the Repeating Issues app. This happened sometimes in some environments and caused ui glitches
3.9.5Jira Server 7.2.0 - 8.15.12021-02-22Bug fix Bug fix
- Fixed a bug that prevented users from viewing the project automation page for the Repeating Issues app. This happened sometimes in some environments and caused ui glitches
3.9.4Jira Data Center 7.2.0 - 8.15.12021-02-04Jira 8.15 compatibility Jira 8.15 compatibility
3.9.4Jira Server 7.2.0 - 8.15.12021-02-04Jira 8.15 compatibility Jira 8.15 compatibility
3.9.3Jira Data Center 7.2.0 - 8.14.12020-12-01Jira 8.14 compatibility Jira 8.14 compatibility
3.9.3Jira Server 7.2.0 - 8.14.12020-12-01Jira 8.14 compatibility Jira 8.14 compatibility
3.9.2Jira Data Center 7.2.0 - 8.13.62020-10-13Jira 8.13 compatibility Jira 8.13 compatibility
3.9.2Jira Server 7.2.0 - 8.13.62020-10-13Jira 8.13 compatibility Jira 8.13 compatibility
3.9.1Jira Data Center 7.2.0 - 8.12.32020-09-06Bug fix Bug fix
- Switch Jira API to prevent possible random errors caused by handling issue events and applying project automation rules
3.9.1Jira Server 7.2.0 - 8.12.32020-09-06Bug fix Bug fix
- Switch Jira API to prevent possible random errors caused by handling issue events and applying project automation rules
3.9.0Jira Data Center 7.2.0 - 8.11.12020-07-20New features, improvements and major fix Feature
- Project automation that allows to set details of the repeating when an issue is created. [more...]
- Next occurrence column with next occurrence date and readable recurrence info available in issue navigator and 'Filter results' dashboard gadget. [more...]
Improvement
- Issue description is now available in email notifications sent by app.
- Calculated due date value is now available in velocity context as $repeating.dueDate. [more...]
Bug fix
- Fixed case when there are UI glitches when the bulk change operation is initiated via the "Bulk operation" selection of the "… " menu beside "Sub-Tasks"
3.9.0Jira Server 7.2.0 - 8.11.12020-07-20New features, improvements and major fix Feature
- Project automation that allows to set details of the repeating when an issue is created. [more...]
- Next occurrence column with next occurrence date and readable recurrence info available in issue navigator and 'Filter results' dashboard gadget. [more...]
Improvement
- Issue description is now available in email notifications sent by app.
- Calculated due date value is now available in velocity context as $repeating.dueDate. [more...]
Bug fix
- Fixed case when there are UI glitches when the bulk change operation is initiated via the "Bulk operation" selection of the "… " menu beside "Sub-Tasks"
3.8.3Jira Data Center 7.2.0 - 8.10.12020-05-15Improvement and bug fix Improvement
- Update documentation about cloning and notifying watchers and add links to this documentation at administration pages.
-
Do not copy inactive users from custom field of single/multi user type when executing 'Clone issue' action. That prevents from failing the 'Clone issue' action with message 'customfield_XXXXX: User 'xxxxxx' is not valid for this user picker'.
Bug fix
- Fixed bug where wrong time zone was used when perform calculations on dates within expressions. When user time zone was different from Jira Server time zone, use of `withHours` method on the date object caused wrong calculation . Now the time zone of user who set repeating is used instead Jira Server time zone and the calculations are valid
3.8.3Jira Server 7.2.0 - 8.10.12020-05-15Improvement and bug fix Improvement
- Update documentation about cloning and notifying watchers and add links to this documentation at administration pages.
- Do not copy inactive users from custom field of single/multi user type when executing 'Clone issue' action. That prevents from failing the 'Clone issue' action with message 'customfield_XXXXX: User 'xxxxxx' is not valid for this user picker'.
Bug fix
- Fixed bug where wrong time zone was used when perform calculations on dates within expressions. When user time zone was different from Jira Server time zone, use of `withHours` method on the date object caused wrong calculation . Now the time zone of user who set repeating is used instead Jira Server time zone and the calculations are validImprovement and bug fix
3.8.2Jira Data Center 7.2.0 - 8.8.12019-11-08Improvement and bug fix Improvement
- Users can now set empty reporter field, during setup of the repeating. This repeating will clone issue or create sub-task with anonymous user as reporter. This is available only when reporter field is optional in Jira.
Bug fix
- Fixed bug where 'Clone Issue' action fails with message "Could not clone issue because of unexpected error. Please contact with your Jira administrator." when cloning the issue with reporter field set to anonymous
3.8.2Jira Server 7.2.0 - 8.8.12019-11-08Improvement and bug fix Improvement
- Users can now set empty reporter field, during setup of the repeating. This repeating will clone issue or create sub-task with anonymous user as reporter. This is available only when reporter field is optional in Jira.
Bug fix
- Fixed bug where 'Clone Issue' action fails with message "Could not clone issue because of unexpected error. Please contact with your Jira administrator." when cloning the issue with reporter field set to anonymous
3.8.1Jira Data Center 7.2.0 - 8.5.142019-10-16Improvement and bug fix Improvement
- Show user friendly message on bulk operations page that "This operation is no longer available due to disabled or uninstalled provider.". This change is to address the case when Repeating Issues options in bulk operations are not removed when app is disabled. Jira do not provide API to unregister such operations - they are cleared after Jira restart.
Bug fix
- Fixed bug where 'Clone Issue' action fails with message "Could not clone issue because of unexpected error. Please contact with your Jira administrator." when cloning issue with sub-tasks that have set due date field
3.8.1Jira Server 7.2.0 - 8.5.142019-10-16Improvement and bug fix Improvement
- Show user friendly message on bulk operations page that "This operation is no longer available due to disabled or uninstalled provider.". This change is to address the case when Repeating Issues options in bulk operations are not removed when app is disabled. Jira do not provide API to unregister such operations - they are cleared after Jira restart.
Bug fix
- Fixed bug where 'Clone Issue' action fails with message "Could not clone issue because of unexpected error. Please contact with your Jira administrator." when cloning issue with sub-tasks that have set due date field
3.8.0Jira Data Center 7.2.0 - 8.5.142019-09-07Feature & bug fix New feature
- Added new bulk change operation to edit basic details of the repeating: reporter, assignee, and owner (the user who set repeating). Changing the owner within bulk operation is available only for administrator, that helps to fix failing repeatings in case of change the user permissions to create issues.
Bug fix
- [Jira 8] Resolved the problem where repeat issue button throws an error when using it from issue detail view on a Jira Software board
3.8.0Jira Server 7.2.0 - 8.5.142019-09-07Feature & bug fix New feature
- Added new bulk change operation to edit basic details of the repeating: reporter, assignee, and owner (the user who set repeating). Changing the owner within bulk operation is available only for administrator, that helps to fix failing repeatings in case of change the user permissions to create issues.
Bug fix
- [Jira 8] Resolved the problem where repeat issue button throws an error when using it from issue detail view on a Jira Software board
3.7.0Jira Data Center 7.2.0 - 8.3.52019-08-14Data Center release and features Features
- The app is now Data Center approved and can be installed on Jira DC instances.
- Introduced multiple non-working days calendars. Now non-working days can be set in configuration of repeated issue by selecting one of available calendars that are defined in app. [more...]
Technical tasks and improvements
- Shutdown executors when app is unloaded.
- The maximum cache size for CachedImportService has been set to prevent cache grow
- ProjectUpdatedEvent is now executed in a worker thread to prevent potential Jira performance issues.
Bug fixes
- [Jira 8] Fixed problem causing „invalid csv file or missing column” errors when import the data of repeated issues at administration screen.
- Fixed case with potential ClassCastException when executing the „reopen issue workflow” repeating that was created with app versions before 2.0.0
3.7.0Jira Server 7.2.0 - 8.3.52019-08-16Data Center release and features Features
- The app is now Data Center approved and can be installed on Jira DC instances.
- Introduced multiple non-working days calendars. Now non-working days can be set in configuration of repeated issue by selecting one of available calendars that are defined in app. [more...]
Technical tasks and improvements
- Shutdown executors when app is unloaded.
- The maximum cache size for CachedImportService has been set to prevent cache grow
- ProjectUpdatedEvent is now executed in a worker thread to prevent potential Jira performance issues.
Bug fixes
- [Jira 8] Fixed problem causing „invalid csv file or missing column” errors when import the data of repeated issues at administration screen.
- Fixed case with potential ClassCastException when executing the „reopen issue workflow” repeating that was created with app versions before 2.0.0
3.6.3Jira Server 7.2.0 - 8.3.52019-06-05Bug fix Bug fix
- Resolved a problem where the next occurrence date is sometimes calculated incorrectly for repeating with rule "1st working day of the month" or "last working day of the month".
3.6.2Jira Server 7.2.0 - 8.2.62019-05-23Improvements & bug fixes Improvements
- Improved solution for handling inconsistent month abbreviations for Deutsch language (supporting März, Mär, Mrz abbreviation for March month)
- Stopped logging invalid JQL with ERROR level when filtering issues at app administration view. Since now, WARN level is used and proper message is displayed on UI.
Bug fixes
- [Jira 8] Fixed bug where it is not possible to edit repeating with monthly frequency and repeated by 'day of the week', when use custom date format (e.g. 'dd.MM.yyyy')
- Fixed bug where it is not possible to setup bulk repeatings using Jira native bulk changes.
3.6.1Jira Server 7.2.0 - 8.1.32019-05-06Bug fixing Bug
- [PRI-126] - UPM self update process interrupts all repeatings
3.6.0Jira Server 7.2.0 - 8.1.32019-04-15Improvements 3.5.0Jira Server 7.2.0 - 8.1.32019-03-28Improvements & bug fix Improvement/New Feature
- [PRI-116] - Checking and reporting for interrupted repeatings
- [PRI-119] - Supporting more Jira system fields in scheduled actions
- [PRI-120] - Add new link to add-on configuration on Jira Administration > Add-ons page
Bug
- [PRI-117] - Could not provide values for required Jira system fields when schedule create sub-task action
3.4.0Jira Server 7.2.0 - 8.0.32019-02-27Maintenance and bugfixing Improvement and Tasks
Bug
- [PRI-112] - Different date formats in date picker and datetime picker cause invalid monthly repeatings
3.3.0Jira Server 7.2.0 - 8.0.32019-02-19Bugfixing Bug
- [PRI-110] - Repeating with no assignee (unassigned) keeps picking up original issue assignee
3.2.0Jira Server 7.2.0 - 8.0.32019-02-11Maintenance taks and improvements 0.18.0Jira Server 7.0.0 - 7.12.32018-08-13Feature Features
- Math operations on date attribute (more in documentation)
0.17.1Jira Server 7.0.0 - 7.11.22018-07-25Jira 7.11.x support and minor bugfixing Bugfixes:
- Menu "More > Repeat" do not work on JIRA 7.10+
- StackOverflowError when adherence non-working days that should be skipped
0.17.0Jira Server 7.0.0 - 7.10.22018-07-06CSV Import feature added CSV import feature. See documentation
0.16.0Jira Server 7.0.0 - 7.10.22018-06-25Repeated issues administration page and minor improvements/fixes Improvement
- Change to SearchService API to prevent index AlreadyClosedException
- Use ${sourceIssue.summary} variable in default repeating summary
- Update marketing assets
- Set proper default members for add-on project roles in Jira Software
New Feature
- Administration screen with all repeatings and their states
Bug
- Repeat button stopped work when using bulk change with edit issues repeatings
0.15.4Jira Server 7.0.0 - 7.10.22018-06-06Minor bugfixing Bugfix
- Resolved date is equal with created date when there is default resolution setup in Jira
0.15.3Jira Server 7.0.0 - 7.10.22018-05-09Bugfixing Bugfix:
- Invalid timezone returned by Jira API for logged in user
0.15.2Jira Server 7.0.0 - 7.9.22018-05-02Major bug fixing Bugfix
- On some instances index is locked when Jira startup
0.15.1Jira Server 7.0.0 - 7.9.22018-05-01Minor bugfixing Bugfix
- Scheduled jobs with invalid key remains in scheduler when project is renamed
0.15.0Jira Server 7.0.0 - 7.9.22018-03-29Improved permissions management This change introduce global enable / disable permissions for Repeating Issues add-on. Now, after installation the permissions are disabled by default and all users can edit / view repaeatings details. For more details please read documentation
0.14.0Jira Server 7.0.0 - 7.8.42018-03-19Improvements and new features Features
- Repeating add-on project permissions. Read more...
- Notify watchers when issues are cloned/created
Improvements
- Enable variables in issue description for Clone Issue action
- Update German translations
- Update add-on banner for marketplace listings
0.13.0Jira Server 7.0.0 - 7.8.42018-03-01Improvements and maintenance - Conflict prevention has been improved with other add-ons that use AngularJs.
- German translations has been added (Thanks to our customers :) )
- New help links to new wiki documentation has been added
0.12.0Jira Server 7.0.0 - 7.8.42018-02-26Features and maintenance Features
- Support component Jira System field when repeat with create sub-task action
- Support description Jira System field when repeat with create sub-task action
- Enable/improve form validation
Maintenance
- Switch from in-house jira-home in project to dependency
0.11.3Jira Server 7.0.0 - 7.8.42019-02-12Fixes Bugfix
- Invalid whitespace character in user name after edit repeating
0.10.4-jira6Jira Server 6.3 - 6.4.142019-02-25Fixes Bugfix
- Invalid whitespace character in user name after edit repeating
0.11.2Jira Server 7.0.0 - 7.5.42019-02-25Fixes Fixed dead link to configuration page
0.11.1Jira Server 7.0.0 - 7.5.42019-02-25Compatibility with third vendors add-on Compatibility with new version of BigGantt add-on (by SoftwarePlant)
0.11.0Jira Server 7.0.0 - 7.4.62019-02-25Data Center compatibility and bugfix Improvements
- Jira Data Center compatibility
Bugfix
- Can't set repeating for users with single quote in their name
0.10.1-jira6Jira Server 6.3 - 6.4.142019-02-25Bugfixing Bugfix
- Can't set repeating for users with single quote in their name
0.10.0-jira6Jira Server 6.3 - 6.4.142019-02-25Features and improvements Features:
- Add repeated issues source and instances links to repeating info panel
- Modifying multiple issues repeating (bulk change)
- Clone action options administration page
- Option to clone watchers
- Options to not clone archived versions
Improvements:
- Fix duplicated resource loading
- Add help link to execution error message
0.9.2Jira Server 7.0.0 - 7.3.92019-02-25Improvements Improvements:
- Do not send success notification when not being a watcher
- Do not allow to set the repeating without any future occurrence
0.9.1Jira Server 7.0.0 - 7.3.92019-02-25Bugfixing Bugfix
- Delete button on repeating dialog does not work in Jira dashboard and Aagile board
- Disappearing scrollbar when navigate back in Jira
0.9.0Jira Server 7.0.0 - 7.3.92019-02-25Features and major changes Features and major changes
- Jira Agile integration - Add option to decide if issue sprint values should be cloned
- Set repeated issue assignee from origin/parent if repeating set-up has not assignee configured (fix assigning for repeatings scheduled before updating add-on to version 0.8.0)
0.9.0-jira6Jira Server 6.3 - 6.4.142019-02-25Features and major changes Features and major changes
- Jira Agile integration - Add option to decide if issue sprint values should be cloned
- Set repeated issue assignee from origin/parent if repeating set-up has not assignee configured (fix assigning for repeatings scheduled before updating add-on to version 0.8.0)
0.8.0Jira Server 7.0.0 - 7.3.92019-02-25Added assignee field and emails for repeating action creator Features and major changes
- Allow to set assignee of repeating issues
- Introduce emails for repeated actions creator
- Add Delete button to repeating configuration dialog
0.7.1Jira Server 7.0.0 - 7.3.92019-02-25Marketplace info update and major improvements (no conflicts with other add-ons) Features and major changes
- Support due date with non-working days adherence when cloning sub-tasks
- Update marketplace listings
- Update Angular version
- Improve Angular no-conflict to prevent conflicts with other add-ons
- Use repeating reporter also in cloned sub-tasks
- Help links to documentation
0.7.0Jira Server 7.0.0 - 7.3.92019-02-25New features - working days adherence and others Features and major changes
- Check and rebuild context for resources
- Improve some translations
- Implement noconflict for AngularJs
- Support scheduling for issue due date with working days adherence
- Non-working days administration screen
Fixes
- Remove me from watchers fails repeating when watching is disabled
- Complex custom fields (e.g. cascading select) not cloned properly
0.6.2Jira Server 7.0.0 - 7.2.152019-02-25Bugfixing Bugfix
- Could not clone issue when labels field is set as required
0.6.2-jira6Jira Server 6.3 - 6.4.142019-02-25Bugfixing Bugfix
- Could not clone issue when labels field is set as required
0.6.1Jira Server 7.0.0 - 7.2.152019-02-25Bugfixing Bugfix
- Fix for original estimates when cloning - wrong unit
0.6.0Jira Server 7.0.0 - 7.2.152019-02-25New feature Features
- Support parametrs in issue summary for cloned sub-task of parent issue
0.5.0Jira Server 7.0.0 - 7.2.152019-02-25Jira 7.2.x compatibility and new feature Features
- Jira 7.2.x compatibility
- Support parametrs in issue summary when clone and create subtask. Available params: ${sourceIssueKey}, ${repeatingDateTime}, ${repeatingDate}, ${repeatingDateIso}, ${repeatingTime}, ${repeatingDay}, ${repeatingMonth}, ${repeatingWeek}, ${repeatingYear}
0.4.0Jira Server 7.0.0 - 7.1.102019-02-25New features and small fix Features
- Clone issue labels
- Support reporter param for create subtask
- Add remove creator from watcher option
- Support repeating definition for every 1st and last working day of the month
Fixes
- Problem with issue assignee user (user does not exist)
0.3.7Jira Server 7.0.0 - 7.1.102019-02-25Major fixes and small UI improvements Fixes
- Problem with edit repeating
0.3.5Jira Server 7.0.0 - 7.1.102019-02-25Support reporter parameter for cloned issue and major fixes Features
- Ability to set reporter of repeating issues when cloning issue
Fixes
- Invalid date format when cloning issue
- User does not exist error when cloning issue
- Error when copying custom field values for cloned issue
0.3.3Jira Server 7.0.0 - 7.1.102019-02-25Major fixes Fixes
- Fix issues with required fields during creating new issues with add-on
0.3.2Jira Server 7.0.0 - 7.1.102019-02-25Bugfixes Fixes
- Issues with double quotes in summary breaks Repeating Issues Plugin
0.3.1Jira Server 7.0.0 - 7.1.102019-02-25New issue cloning features and minor fixes Features
- Add option to decide if links should be cloned
- Add option to decide if sub-tasks should be cloned
Fixes
- Unsupported unit exception when adjust due date
0.3.0Jira Server 7.0.0 - 7.1.102019-02-25Jira 7.1.x compatibility and support for exact time in repeating issues - Jira 7.1.x compatibility
- Allow to set exact time when recurrence should be executed
- New JQL aliases for searching repeating issues: repeatingIssueRule, repeatingIssueNextDate. Example JQL: "repeatingIssueRule is not empty", "repeatingIssueNextDate > now() and repeatingIssueNextDate< endOfWeek()"
- Bug fixes
0.2.0Jira Server 7.0.0 - 7.0.112019-02-25Jira 7 compatibility and major bugfixes - Jira 7 compatibility
- Make last failed recurrence executions searchable
- Fix: One recurring action fail stops execution of other
0.1.3Jira Server 6.3 - 6.4.142019-02-25Bugfixing Changes:
* Fix missing authentication context when executing repeating actions