Skip to main content

Activity Events > Author

Arnaud Lachaume avatar
Written by Arnaud Lachaume
Updated over a week ago

Dataset: Activity Events

Entity: Activity Events

Field ID: author_username

Type: Text

Description: The username of the person who created the event. Note that usernames are app-specific.

Source: Applications support the following events

  • Github: CREATED, CLOSED, REOPENED, MERGED, REVIEWER_ASSIGNED, REVIEWER_UNASSIGNED, USER_ASSIGNED, USER_UNASSIGNED

  • GitLab: CREATED, CLOSED, REOPENED, MERGED, REVIEWER_ASSIGNED, REVIEWER_UNASSIGNED, USER_ASSIGNED, USER_UNASSIGNED, WORK_LOGGED

  • Bitbucket: CREATED, CLOSED, MERGED, REVIEWER_ASSIGNED, REVIEWER_UNASSIGNED

  • Azure DevOps: CREATED, CLOSED, MERGED, REVIEWER_ASSIGNED, REVIEWER_UNASSIGNED

  • Jira: CREATED, CLOSED, REOPENED, USER_ASSIGNED, USER_UNASSIGNED, WORK_LOGGED, WORKFLOW_STATUS_UPDATED

  • ClickUp: CREATED, CLOSED. ClickUp does not expose an events API. Keypup generates these two events based on the issue timestamps (date_created & date_closed)

  • Trello: CREATED, CLOSED, REOPENED, USER_ASSIGNED, USER_UNASSIGNED, WORKFLOW_STATUS_UPDATED

Transformation logic: N/A

From:

Github (Timeline Items)

actor.login

Gitlab (Discussions, State Events)

Discussions: author.username
​State Events: user.username

Bitbucket (Activity)

update.author.uuid

Azure DevOps (PR Threads)

Extracted from identities and matched against the thread message.

Jira (Changelog, Worklog)

Cloud: author.accountId

Data Center: author.key

ClickUp (Issue timestamps)

CREATED: creator.id
​CLOSED: null (The ClickUp API does not expose the user who closed the issue)

Trello (Actions)

idMemberCreator

Reporting Use Cases

The Author field from the Activity Events dataset identifies the user who performed a specific action, making it essential for creating detailed activity feeds and analyzing the contribution patterns of different team members over time.

  • Filtering for Activity Feeds: You can create highly specific feeds by filtering events based on who performed them.

    • Personal Activity Log: To see a log of all your own actions (e.g., issues you've closed, PRs you've merged), use a filter where Author is me.

    • Team Activity Stream: Create a report showing all actions taken by a specific team by filtering where Author equals any of "user1,user2".

    • Exclude Automated Actions: A crucial use case is to remove noise from automated systems by applying a filter like Author !~ "bot".

  • Reporting on Contributor Activity: Using author_username as a dimension allows you to see who is most active and what kinds of actions they are performing.

    • Top Contributors: A bar chart with Author as the dimension and COUNT() as the metric will show who is generating the most activity events.

    • Activity Breakdown by User: You can create a heatmap or stacked bar chart with Author as one dimension and action as the other. This can reveal important patterns, such as which team members are most involved in closing issues (CLOSED) versus assigning work (USER_ASSIGNED).

  • Custom Formulas for High-Level Metrics: You can use this field in aggregations to get a broader view of team engagement.

    • Active User Count: A KPI with the custom formula COUNT_DISTINCT(author_username) can tell you the number of unique team members who performed any action in a given time period, which is a great measure of overall team engagement.

Did this answer your question?