Minor version update

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)

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)

Jira 9.10 compatibility

Jira 9.10 compatibility

Jira 9.9 compatibility

Jira 9.9 compatibility

Fixed a bug that causing migration to fail when Jira Server instance use non UTF-8 encoding.

Fixed a bug that causing migration to fail when Jira Server instance use non UTF-8 encoding.

Jira 9.8 compatibility

Jira 9.8 compatibility

Jira 9.7 compatibility

Jira 9.7 compatibility

Fixed a bug that causing none issues are migrated to cloud when project key is like a word from JQL syntax, e.g. "IN"

Fixed a bug that causing none issues are migrated to cloud when project key is like a word from JQL syntax, e.g. "IN"

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

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

Jira 9.5 compatibility

Jira 9.5 compatibility

Improvements

• Jira 9.4 compatibility

Bug fixes

• Fix a bug where migration to cloud process may ends as incomplete

Improvements

• Jira 9.4 compatibility

Bug fixes

• Fix a bug where migration to cloud process may ends as incomplete

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

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

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

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

Cloud migration bug fix

Cloud migration bug fix

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

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

Jira 9 compatibility

Jira 9 compatibility

Features:

• Support for migration to Jira Cloud (more...)
• Ability to search issues with repeating by its owner in JQL: codedoers.repeating.owner = anyuserkey

Features:

• Support for migration to Jira Cloud (more...)
• Ability to search issues with repeating by its owner in JQL: codedoers.repeating.owner = anyuserkey

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.

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.

Jira 8.21 compatibility

Jira 8.21 compatibility

Jira 8.20 compatibility

Jira 8.20 compatibility

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...".

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...".

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.

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.

Added compatibility for Jira 8.18.1

Added compatibility for Jira 8.18.1

Added compatibility for Jira 8.17

Bug fix:

• Resolved a bug where project administrators are not able to edit project automation rules

Added compatibility for Jira 8.17

Bug fix:

• Resolved a bug where project administrators are not able to edit project automation rules

Jira 8.16 compatibility

Jira 8.16 compatibility

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

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

Jira 8.15 compatibility

Jira 8.15 compatibility

Jira 8.14 compatibility

Jira 8.14 compatibility

Jira 8.13 compatibility

Jira 8.13 compatibility

Bug fix

• Switch Jira API to prevent possible random errors caused by handling issue events and applying project automation rules

Bug fix

• Switch Jira API to prevent possible random errors caused by handling issue events and applying project automation rules

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"

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"

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

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

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

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

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

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

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

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

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

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

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".

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.

Bug

• [PRI-126] - UPM self update process interrupts all repeatings

New Feature

• [PRI-2] - Add option to decide if attachments should be cloned

Bug

• [PRI-124] - App administration pages should be accessible for both "Jira System Administrators" and "Jira Administrators" permissions

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

Improvement and Tasks

• [PRI-113] - Translations and little admin UI updates
• [PRI-114] - Update OSGI imports

Bug

• [PRI-112] - Different date formats in date picker and datetime picker cause invalid monthly repeatings

Bug

• [PRI-110] - Repeating with no assignee (unassigned) keeps picking up original issue assignee

• [PRI-103] - Handle inactive users during action execution
• [PRI-106] - Reset all permissions rest endpoint for administrators
• [PRI-102] - In app help for repeatings with interrupted status
• [PRI-105] - Update German translations

Features

• Math operations on date attribute (more in documentation)

Bugfixes:

• Menu "More > Repeat" do not work on JIRA 7.10+
• StackOverflowError when adherence non-working days that should be skipped

CSV import feature. See documentation

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

Bugfix

• Resolved date is equal with created date when there is default resolution setup in Jira

Bugfix:

• Invalid timezone returned by Jira API for logged in user

Bugfix

• On some instances index is locked when Jira startup

Bugfix

• Scheduled jobs with invalid key remains in scheduler when project is renamed

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

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

• 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

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

Bugfix

• Invalid whitespace character in user name after edit repeating

Bugfix

• Invalid whitespace character in user name after edit repeating

Fixed dead link to configuration page

Compatibility with new version of BigGantt add-on (by SoftwarePlant)

Improvements

• Jira Data Center compatibility

Bugfix

• Can't set repeating for users with single quote in their name

Bugfix

• Can't set repeating for users with single quote in their name

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

Improvements:

• Do not send success notification when not being a watcher
• Do not allow to set the repeating without any future occurrence

Bugfix

• Delete button on repeating dialog does not work in Jira dashboard and Aagile board
• Disappearing scrollbar when navigate back in Jira

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)

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)

Features and major changes

• Allow to set assignee of repeating issues
• Introduce emails for repeated actions creator
• Add Delete button to repeating configuration dialog

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

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

Bugfix

• Could not clone issue when labels field is set as required

Bugfix

• Could not clone issue when labels field is set as required

Bugfix

• Fix for original estimates when cloning - wrong unit

Features

• Support parametrs in issue summary for cloned sub-task of parent issue

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}

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)

Fixes

• Problem with edit repeating

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

Fixes

• Fix issues with required fields during creating new issues with add-on

Fixes

• Issues with double quotes in summary breaks Repeating Issues Plugin

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

• 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

• Jira 7 compatibility
• Make last failed recurrence executions searchable
• Fix: One recurring action fail stops execution of other

Changes:

* Fix missing authentication context when executing repeating actions