...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Importing data from CSV file
The Repeating Issues add-on, allows you to import repeating issues details from a comma-separated value (CSV) file. CSV files are text files representing tabulated data and are supported by most applications that handle tabulated data (for e.g. Microsoft Excel, databases, etc.).
...
| Property | Description | Values | ||
|---|---|---|---|---|
| rRule | Recurrence rule defined as RFC 2445. Together with startDate and actionParams.scheduleType this will define when repeating will trigger. | Any string representing rule in RFC 2445. Examples
| ||
| action | Action that should be repeated. | One of:
| ||
| startDate | Defines the start date and time relative to which subsequent occurrences are calculated on the recurrence rule. | A full date and time without millis, separated by a 'T' (yyyy-MM-dd'T'HH:mm:ssZZ) in Jira default time zone. Example:
| ||
| actionParams.summary | Summary that will be set to new cloned issue. This field can have parameters like ${repeatingDate} - for details please follow Available variables in repeating action param strings | Any string. | ||
| actionParams.reporter | User which will be set as reporter of new cloned issue or new created sub-task. | Jira "username" as string. Example:
| ||
| actionParams.assignee | User which will be set as assignee of new cloned issue or new created sub-task. | Jira "username" as string. Example:
| ||
| actionParams.scheduleType | Defines which issue date should be repeated: issue create date or issue due date. This is equivalent for "Repeat for" field in UI form. See Scheduling Clone Issue action for details. | One of:
| ||
| actionParams.issueDuration | The number of working days between new cloned issue created date and due date. Please read how to configure non-working days. | Positive integer value. | ||
| actionParams.cloneLinks | When true - all source issue links (excluding Clone link) will be cloned to new cloned issue. | Boolean value: true/false. | ||
| actionParams.cloneSubTasks | When true - all sub-tasks from source issue will be cloned as sub-tasks to new cloned issue. | Boolean value: true/false. | ||
| actionParams.cloneSprintValues | When true and Jira Agile is available - sprint field values from source issue will be also cloned to new cloned issue. | Boolean value: true/false. | ||
| actionParams.preventAutoWatch | When true - the creator will not be notified of any changes to new cloned issue. This is equivalent for "Remove me from watchers" field in UI form. See Scheduling Clone Issue action for details. | Boolean value: true/false. | ||
| actionParams.notifyWatchers | When true - watchers of new created issue will be notified via email. See Email notifications. | Boolean value: true/false. | ||
| actionParams.issuetype | Issue type of new created sub-task. | Project issue type id as string. | ||
| actionParams.components | Project components which will be set to new sub-task issue. | List of project component id as string. | ||
| actionParams.description | Description that will be set to new sub-task issue. This field can have parameters like ${repeatingDate} - for details please follow Available tokens in action param strings | Any string. | ||
| actionParams.workflowId | The transition of current workflow related with issue project that should be executed. | Id of workflow transition as string. |
...