Recurring Task Cloud Releases

• Minor improvements

• Repeat Issue feature - notify users about issue repetition failures via e-mail. You can configure in "Repeat Issue" panel of issue view which users will be emailed about issue repetition failures. 

• Minor update

• New way of issue creation on schedule - repeat existing issue. Open selected issue in Jira, go to "Repeat Issue" panel, set the scheduling and turn on the toggle. Your issue will be repeated on schedule. More information can be found at Repeat existing JIRA issue page. See also the differences of classic recurring task and the new repeat issue feature.

• "Move Tasks" bulk operation introduced. This operation allows to migrate recurring tasks to other projects or change their issue types
• Minor improvements

• Minor improvements
  • Task list rendering optimisation

• Minor improvements

• Sorting task list introduced. The list can be sorted by columns: Name, Issue Summary, Enable, Starts on Date, Ends on Date, Next Run, Timezone, Project, Last Run, Owner.

• Timezone of a task can be set explicitly in UI. It helps administrators to create recurring tasks for team spread all across the world. The task list shows all times respecting each task timezone.

• Minor UI improvements.

• Minor improvements

• "Every n years" scheduling rule fixed

• Editing task with non-existing issue type fixed
• Minor improvements

• Minor UI improvements

• Epic Link field - allow to set Jira issue with custom epic issue type.

• Minor bug fixes

• Minor improvements

• Minor improvements

• Take action on multiple tasks at the same time - bulk operation introduced

Go to the task list menu in right upper corner and select "Bulk change" to make bulk operation. There are following operations available:

• Change Owner
• Change Reporter
• Change Assignee
• Change Due Date
• Disable Tasks
• Enable Tasks
• Remove Tasks

• Task owner editing by Jira admin fixed

• Use user time zone in UI

• Minor version update

• Minor version update

• Minor version update

This version adds setting initial status of newly created issue. You don't have to look for a new issue in Backlog. Just set "Issue Status" field in a task to "Selected for Development" and the new issue goes to relevant column of your Kanban board right away.

The new functionality requires ADMIN privilege. The application also requests ACT_AS_USER and ACCESS_EMAIL_ADDRESSES privileges to implement another important features in the nearest future.

• "Access Recurring Tasks" Jira global permission added.  The new permission allows to control who can view and create tasks in the app.

• Compliance with Atlassian Security Requirements

• Minor version update

• Minor version update

• Minor version update

• Minor version update

• Minor improvements in UI

• Some Jira instances have a problem with returning assignable users due to a bug in Jira. That is why Assignee field could not be set in the app. As a workaround the application shows all users in Assignee lookup until Atlassian fixes the bug.

• Minor improvements for Service Desk

• Getting Started page added to quickly introduce the app

• Epic handling for subtask issues fixed

• Minor improvements

• Improvements related to next-gen projects and sprints

• Fixed Scrum Board field editing when specified board does not exist any more
• "All Executions" menu added to Jira sidebar

• Future Sprint search fixed
• Saving large number of error messages fixed

RELEASED

• Recurring subtasks are created in the fixed order matching the order in the task list 
• Tasks owned by users deleted in Jira are disabled automatically
• Jira administrator may edit all recurring tasks
• Changes that improve the user experience 

• Minor improvements

• Security Level field support added
• Jira administrator may delete any task
• Internal improvements 

• Tempo Account field handling fixed
• Time Zone name that contains "+" character is interpreted in the right way now

• Fields validation in the 'Status' task list column fixed. No more false positive validation errors with 'Account' field.

• "Create Recurring Task from issue" action fills Assignee, Reporter, Single/Multiple user picker fields in 'Add Recurring Task' dialog again
• Number of REST calls fetching user data reduced 
• Better error handling of 'Run Now' action

• Changes related to  European General Data Protection Regulation (GDPR) that improves user privacy implemented. The changes are requested by Atlassian and they are addressed  to all Atlassian Marketplace vendors. Technical information can be found here
• Time zone is no longer taken from web browser settings but read from Jira user personal settings instead
• "Owner" task list column displays full user name now
• User Picker (multiple users) custom field not showing stored users fixed

• False date macro warnings fixed
• Internal improvements

• User interface updated to follow Atlassian look and feel

See more task scheduling examples

• 'Next Run' column of Recurring Tasks list always shows correct date
• UI date format fixed

RT-13 - Allow to set relative due date

RT-40 - Allow to set epic link (if epic links is available in JIRA)

RT-45 - Highlight current (mouseover) template line on the list

RT-72 - Support for system field Linked Issues

RT-83 - Assignee and label fields are blank during edit

RT-91 - Issue with RequireJS script loading

RT-93 - List all viable users in "assignee"/"reporter" fields (not only 10)

RT-67 - Support for sub-tasks

RT-71 - Support for system field Fix Versions

RT-87 - Support for Affects Versions field

RT-70 - Support for system field Components