DELETE /rest/api/2/issue/{issueIdOrKey}/worklog
Deletes a list of worklogs from an issue. This is an experimental API with limitations:
- You can't delete more than 5000 worklogs at once.
- No notifications will be sent for deleted worklogs.
Time tracking must be enabled in Jira, otherwise this operation returns an error. For more information, see Configuring time tracking.
Permissions required:
- Browse projects project permission for the project containing the issue.
- If issue-level security is configured, issue-level security permission to view the issue.
- Delete all worklogsproject permission to delete any worklog.
- If any worklog has visibility restrictions, belongs to the group or has the role visibility is restricted to.
Servers
- https://your-domain.atlassian.net
Path parameters
Name | Type | Required | Description |
---|---|---|---|
issueIdOrKey |
String | Yes |
The ID or key of the issue. |
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
overrideEditableFlag |
Boolean | No |
Whether the work log entries should be removed to the issue even if the issue is not editable, because jira.issue.editable set to false or missing. For example, the issue is closed. Connect and Forge app users with admin permission can use this flag. Default value: false |
adjustEstimate |
String | No |
Defines how to update the issue's time estimate, the options are:
Possible values:
Default value: "auto" |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
ids[] |
Array | Yes |
A list of worklog IDs. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.