Audit logs

Audit logs let you track key events and employee activity in your organization. This can be useful in case of incidents and security breaches.

Using audit logs, organization administrators and audit log managers can see what actions employees perform in Tracker. For example, creating and editing issues and projects, changing queue settings, creating issue boards and dashboards.

How to enable

The ability to use audit logs depends on your organization’s Yandex 360 plan. Plans and their features are described in the Yandex 360 Help.

To use audit logs, an administrator needs to enable this feature in the organization’s account. How to enable audit logs

After enabling audit logs, the administrator must notify all users about it and, if necessary, obtain their written consent (if they haven’t given it before).

How to view logs

To view audit logs, use the Yandex 360 API. You cannot view Tracker audit logs in the organization’s account.

To work with the API, you’ll need:

  • OAuth token with permissions to access audit logs: ya360_security:read_auditlog. To get a token, follow the instructions on the API access page.

  • Organization ID: open the organization’s account and select General settingsOrganization profile. The ID will be shown under the organization’s name.

To retrieve logs, form a request:

curl -X GET -H "Authorization: OAuth {oauth_token}" https://cloud-api.yandex.net/v1/auditlog/organizations/{org_id}/events?ended_at={ended_at}&count={count}

Substitute the required values into the code:

  • {org_id} — organization ID;
  • {oauth_token} — OAuth token;
  • {ended_at} — end date and time of the audit log in ISO 8601 format, for example 2024-01-31T23:59:59;
  • {count} — number of events per results page, from 1 to 100.

You’ll find a full description of all methods for retrieving audit logs in the Yandex 360 API documentation.

List of events

List of Tracker events recorded in the logs:

Event name

Description

Parameters

tracker_entity-access-updated

A change in a user's, group's, or role's access permissions to a Tracker entity.

List of event parameters
  • entity_type — the entity type. Valid values:
    • queue — queue,
    • board — board,
    • dashboard — dashboard,
    • project — project,
    • portfolio — portfolio,
    • goal — goal,
    • report — report,
    • component — component,
  • entity_id — the entity's internal ID,
  • entity_short_id — the entity's short numeric ID,
  • entity_key — the entity key (for example, MYQUEUE),
  • entity_name — the entity name,
  • source — the event source,
  • users — the list of users whose permissions changed. Each element contains:
    • passport_id — the user ID,
    • login — the user's login,
    • display — the user's display name,
    • is_robot — whether the user is a robot,
    • email — the user's email,
    • access.old_value — the list of permissions before the change,
    • access.new_value — the list of permissions after the change,
  • groups — the list of groups whose permissions changed. Each element contains:
    • directory_id — the group ID in Directory,
    • display — the group's display name,
    • type — the group type,
    • access.old_value — the list of permissions before the change,
    • access.new_value — the list of permissions after the change,
  • roles — the list of roles whose permissions changed. Each element contains:
    • id — the role ID,
    • ru_display — the role's display name,
    • access.old_value — the list of permissions before the change,
    • access.new_value — the list of permissions after the change.

tracker_issue-access-updated

A change in a user's access permissions to an issue — for example, when a component with restricted access is added.

List of event parameters
  • issue_id — the issue's internal ID,
  • issue_key — the issue key (for example, MYQUEUE-42),
  • source — the event source,
  • components — the components whose change caused the access permissions to change:
    • added[] — the added components. Each element contains:
      • id — the component ID,
      • name — the component name,
    • removed[] — the removed components. Each element contains:
      • id — the component ID,
      • name — the component name,
  • fields[] — the issue fields whose change caused the access permissions to change. Each element contains:
    • id — the field ID,
    • ru_display — the field's display name,
    • users — the users whose permissions changed:
      • added[] — the users who were granted access. Each element contains:
        • passport_id — the ID,
        • login — the login,
        • display — the display name,
        • robot — whether the user is a robot,
        • email — the email,
      • removed[] — the users who lost access (same fields).

tracker_issue-created

Creating an issue.

List of event parameters
  • issue_id — the issue's internal ID,
  • issue_key — the issue key (for example, MYQUEUE-42),
  • source — the event source,
  • executed_triggers[] — the triggers that fired when the issue was created. Each element contains:
    • short_id — the trigger's short ID,
    • name — the trigger name,
  • applied_autoactions — the auto action that fired when the issue was created:
    • short_id — the auto action's short ID,
    • name — the auto action name.

tracker_issue-updated

Changing an issue — updating fields or changing the status.

List of event parameters
  • issue_id — the issue's internal ID,
  • issue_key — the issue key (for example, MYQUEUE-42),
  • source — the event source,
  • executed_macros — the macro applied when the issue was changed:
    • short_id — the macro's short ID,
    • name — the macro name,
  • executed_triggers[] — the triggers that fired when the issue was changed. Each element contains:
    • short_id — the trigger's short ID,
    • name — the trigger name,
  • applied_autoactions — the auto action that fired when the issue was changed:
    • short_id — the auto action's short ID,
    • name — the auto action name,
  • changes[] — the list of changed issue fields. Each element contains:
    • field_id — the field ID,
    • field_type — the field type: system — system, custom — custom, local — local,
    • ru_display — the field's display name.

tracker_issue-cloned

Cloning an issue.

List of event parameters
  • source_issue_id — the source issue's internal ID,
  • source_issue_key — the source issue key (for example, MYQUEUE-42),
  • new_issue_id — the new issue's internal ID,
  • new_issue_key — the new issue key,
  • source — the event source,
  • executed_triggers[] — the triggers that fired during cloning. Each element contains:
    • short_id — the trigger's short ID,
    • name — the trigger name,
  • applied_autoactions — the auto action that fired during cloning:
    • short_id — the auto action's short ID,
    • name — the auto action name.

tracker_issue-moved

Moving an issue to a different queue.

List of event parameters
  • issue_id — the issue's internal ID,
  • source — the event source,
  • old_issue_key — the old issue key before the move,
  • new_issue_key — the new issue key after the move,
  • old_queue_key — the source queue key,
  • new_queue_key — the target queue key.

tracker_issue-comment-added

Adding a comment to an issue.

List of event parameters
  • issue_id — the issue's internal ID,
  • issue_key — the issue key (for example, MYQUEUE-42),
  • source — the event source,
  • author — the comment author:
    • passport_id — the ID,
    • login — the login,
    • display — the display name,
    • is_robot — whether the user is a robot,
    • email — the email,
  • comment — the comment data:
    • id — the comment ID,
    • reply_to — the ID of the comment being replied to,
    • summon_users[] — the mentioned users. Each element contains:
      • passport_id — the ID,
      • login — the login,
      • display — the display name,
      • is_robot — whether the user is a robot,
      • email — the email.

tracker_issue-links-changed

Changing an issue's links — adding, deleting, or changing the link type.

List of event parameters
  • issue_id — the issue's internal ID,
  • issue_key — the issue key (for example, MYQUEUE-42),
  • source — the event source,
  • links — the link changes:
    • added[] — the added links. Each element contains:
      • issue_id — the linked issue's ID,
      • issue_key — the linked issue's key,
      • relationship — the link type,
    • removed[] — the removed links. Each element contains:
      • issue_id — the linked issue's ID,
      • issue_key — the linked issue's key,
      • relationship — the link type,
    • updated[] — the changed links. Each element contains:
      • issue_id — the linked issue's ID,
      • issue_key — the linked issue's key,
      • old_relationship — the previous link type,
      • new_relationship — the new link type.

tracker_metaentity-created

Creating a meta entity — a project, portfolio, goal, or report.

List of event parameters
  • entity_type — the entity type. Valid values:
    • project — project,
    • portfolio — portfolio,
    • goal — goal,
    • report — report,
  • entity_id — the entity's internal ID,
  • entity_short_id — the entity's short numeric ID,
  • source — the event source.

tracker_metaentity-updated

Changing a meta entity — a project, portfolio, goal, or report.

List of event parameters
  • entity_type — the entity type. Valid values:
    • project — project,
    • portfolio — portfolio,
    • goal — goal,
    • report — report,
  • entity_id — the entity's internal ID,
  • entity_short_id — the entity's short numeric ID,
  • source — the event source.

tracker_queue-created

Creating a queue.

List of event parameters
  • queue_id — the queue's internal ID,
  • queue_short_id — the queue's short numeric ID,
  • queue_key — the queue key (for example, MYQUEUE),
  • queue_name — the queue name,
  • source — the event source.

tracker_queue-updated

Changing queue settings — the owner, team, or followers.

List of event parameters
  • queue_id — the queue's internal ID,
  • queue_short_id — the queue's short numeric ID,
  • queue_key — the queue key (for example, MYQUEUE),
  • queue_name — the queue name,
  • source — the event source,
  • lead_change — the queue owner change:
    • old_lead — the previous owner:
      • passport_id — the ID,
      • login — the login,
      • display — the display name,
      • is_robot — whether the user is a robot,
      • email — the email,
    • new_lead — the new owner (same fields),
  • team_change — changes to the queue team:
    • added[] — the added members (fields are the same as in old_lead),
    • removed[] — the removed members (fields are the same as in old_lead),
  • followers_change — changes to the queue's followers:
    • added[] — the added followers (fields are the same as in old_lead),
    • removed[] — the removed followers (fields are the same as in old_lead).

tracker_component-created

Creating a queue component.

List of event parameters
  • queue_id — the queue's internal ID,
  • queue_short_id — the queue's short numeric ID,
  • queue_key — the queue key,
  • queue_name — the queue name,
  • source — the event source,
  • component_id — the component's internal ID,
  • component_short_id — the component's short numeric ID,
  • component_name — the component name.

tracker_component-updated

Changing a queue component.

List of event parameters
  • queue_id — the queue's internal ID,
  • queue_short_id — the queue's short numeric ID,
  • queue_key — the queue key,
  • queue_name — the queue name,
  • source — the event source,
  • component_id — the component's internal ID,
  • component_short_id — the component's short numeric ID,
  • component_name — the component name.

tracker_component-deleted

Deleting a queue component.

List of event parameters
  • queue_id — the queue's internal ID,
  • queue_short_id — the queue's short numeric ID,
  • queue_key — the queue key,
  • queue_name — the queue name,
  • source — the event source,
  • component_id — the component's internal ID,
  • component_short_id — the component's short numeric ID,
  • component_name — the component name.

tracker_automatization-created

Creating an automation in a queue — a trigger, auto action, or macro.

List of event parameters
  • queue_id — the queue's internal ID,
  • queue_short_id — the queue's short numeric ID,
  • queue_key — the queue key,
  • queue_name — the queue name,
  • source — the event source,
  • automatization_type — the automation type: trigger — trigger, autoaction — auto action, macro — macro,
  • automatization_short_id — the automation's short numeric ID,
  • automatization_name — the automation name.

tracker_automatization-updated

Changing an automation in a queue — a trigger, auto action, or macro.

List of event parameters
  • queue_id — the queue's internal ID,
  • queue_short_id — the queue's short numeric ID,
  • queue_key — the queue key,
  • queue_name — the queue name,
  • source — the event source,
  • automatization_type — the automation type: trigger — trigger, autoaction — auto action, macro — macro,
  • automatization_short_id — the automation's short numeric ID,
  • automatization_name — the automation name.

tracker_automatization-deleted

Deleting an automation from a queue — a trigger, auto action, or macro.

List of event parameters
  • queue_id — the queue's internal ID,
  • queue_short_id — the queue's short numeric ID,
  • queue_key — the queue key,
  • queue_name — the queue name,
  • source — the event source,
  • automatization_type — the automation type: trigger — trigger, autoaction — auto action, macro — macro,
  • automatization_short_id — the automation's short numeric ID,
  • automatization_name — the automation name.

tracker_board-created

Creating a board.

List of event parameters
  • board_short_id — the board's internal ID,
  • board_key — the board key,
  • board_name — the board name,
  • source — the event source.

tracker_board-updated

Changing a board — for example, changing the owner.

List of event parameters
  • board_short_id — the board's internal ID,
  • board_key — the board key,
  • board_name — the board name,
  • source — the event source,
  • owner_change — the board owner change:
    • old_owner — the previous owner:
      • passport_id — the ID,
      • login — the login,
      • display — the display name,
      • is_robot — whether the user is a robot,
      • email — the email,
    • new_owner — the new owner (same fields).

tracker_board-deleted

Deleting a board.

List of event parameters
  • board_short_id — the board's internal ID,
  • board_key — the board key,
  • board_name — the board name,
  • source — the event source.

tracker_dashboard-created

Creating a dashboard.

List of event parameters
  • dashboard_short_id — the dashboard's internal ID,
  • dashboard_name — the dashboard name,
  • source — the event source,
  • owner — the dashboard owner:
    • passport_id — the ID,
    • login — the login,
    • display — the display name,
    • is_robot — whether the user is a robot,
    • email — the email.

tracker_dashboard-updated

Changing a dashboard.

List of event parameters
  • dashboard_short_id — the dashboard's internal ID,
  • dashboard_name — the dashboard name,
  • source — the event source,
  • owner_change — the dashboard owner change:
    • old_owner — the previous owner:
      • passport_id — the ID,
      • login — the login,
      • display — the display name,
      • is_robot — whether the user is a robot,
      • email — the email,
    • new_owner — the new owner (same fields).

tracker_dashboard-deleted

Deleting a dashboard.

List of event parameters
  • dashboard_short_id — the dashboard's internal ID,
  • dashboard_name — the dashboard name,
  • source — the event source.

tracker_dashboard-widget-created

Creating a widget on a dashboard.

List of event parameters
  • dashboard_short_id — the internal ID of the dashboard the widget belongs to,
  • widget_short_id — the widget's internal ID,
  • widget_type — the widget type,
  • source — the event source,
  • widget_description — the widget description.

tracker_dashboard-widget-updated

Changing a widget on a dashboard.

List of event parameters
  • dashboard_short_id — the internal ID of the dashboard the widget belongs to,
  • widget_short_id — the widget's internal ID,
  • widget_type — the widget type,
  • source — the event source,
  • widget_description — the widget description.

tracker_dashboard-widget-deleted

Deleting a widget from a dashboard.

List of event parameters
  • dashboard_short_id — the internal ID of the dashboard the widget belongs to,
  • widget_short_id — the widget's internal ID,
  • widget_type — the widget type,
  • source — the event source,
  • widget_description — the widget description.

A widget is a visual element on the dashboard that automatically pulls issue data and displays it as a list, table, or chart.

Dashboard

A dashboard is a page that helps users monitor the status of important issues and view statistics. You can add issue lists, tables, charts, and notes to the dashboard.

Issue board

An issue board is a tool that helps you easily monitor and update issue statuses. On the board, issues are shown as cards distributed across columns of the board depending on their status.

Issue

In Yandex Tracker, you can use issues to register tasks, requests, and other types of work. An issue has a name, assignee, deadline, and other parameters.

Issue key

An issue key is the unique ID of an issue. It consists of the queue key and the sequence number, for example: TEST-123. You can use this key to access the corresponding issue via a link: https://tracker.yandex.com/TEST-123.

Queue key

A queue key is a unique code consisting of Latin characters that helps identify the queue. For example: TEST. You can use this key to access the corresponding queue via a link: https://tracker.yandex.com/TEST.

Queue

A queue is a space for issues that share a common workflow or focus on the same product. Queues can also be used as an issue list meant for a specific team or department. Queues enable you to order your issues and see who is responsible for their execution. How to set up queues

Project

In Yandex Tracker, a project is a set of issues that aim to achieve a common goal within a certain time frame. Every project has a deadline and a lead. Projects can include issues from different queues, which makes them useful for grouping tasks that involve various teams.

Filter

In Yandex Tracker, you can use filters to search for issues by parameters. For example, you can find all issues in queues where you have the author or assignee status.