EaserixDocs
DevelopersAPI referenceTasksActivity

List an issue's activity history

Property-change entries, oldest first, capped at 500, with the actor embedded. from/to hold raw values (ids, numbers, dates) that clients resolve for display.

View as Markdown
GET
/v1/issues/{id}/activities

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string
Formatuuid

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/issues/497f6eca-6276-4993-bfeb-53cbbbba6f08/activities"
{  "activities": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "issueId": "96179c34-d541-49af-b046-c06f0377732c",      "actorId": "d2f1b55c-8cee-4a0d-af57-aebaeff77518",      "actor": {        "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",        "name": "string",        "email": "string"      },      "type": "created",      "from": "string",      "to": "string",      "created": "2019-08-24T14:15:22Z"    }  ]}

Delete a comment (author, or a workspace admin)

The comment's author may delete it, and so may a moderator — someone holding org.teams.manage, or leading the team the comment's issue belongs to. That is the path for removing a comment nobody else can, such as one carrying a pasted credential. Note the asymmetry with updateComment, which stays author-only with no override: an administrator may REMOVE someone's words but never rewrite them, because an edited comment still carries the original author's name. A moderator deletion is recorded in the audit log as `comment.moderated`; deleting your own is not, since that is ordinary use and would bury the entries that matter. Reach is bounded by the comment's issue, so a comment in another workspace is 404 for everyone including an admin — never 403, which would confirm the id names a real comment somewhere.

List an issue's attachments

Newest first. Each url is GET /v1/attachments/{id}/content, which serves the bytes to a caller with a session.