REST API - Configuring Recurring Rule
Introduction
It is possible to configure the OOO period for the users via REST API
List of Attributes
Data Type | Attribute Name | Default Value | Remarks |
---|---|---|---|
String | projectIdString | "-1" | "-1" will be all other project If not, it will be the projectId of project |
String | covererId |
| The coverer username if reassignMode is set to "coverer" Set to "-" for do not re-assign issue |
String | covererAvatar |
| The small avatar img of coverer which is used to populate in recur rule table |
String | covererDisplayName |
| The coverer full name which is used to populate in recur rule table |
String | projectInfo |
| The project name and key which are configured |
String | reassignMode |
| Can use "coverer", for re-assigning issue Can use "unassign", for unassigning issue ( the option is only available if JIRA allow unassign issue) Can use "same", for do not re-assign issue |
String | oneTimeMessage |
| Message to be added into comment should the user is OOO This message will be appended into period's message as comment |
int | oneTimeId | 0 | The id of the recur rule for update and delete rule |
REST APIs