When ever a person adds a comment or attaches and image in the comments, it seems there is not event for it, is there any way to get that event or any way to find out when a comment is added to a version, task or shot/asset?
Would you like to run some automations when some one make a comment in the details panel?
For information, users should get notifiactions when a comment is made as outlined in Inbox and Notifications .
yes, i am trying to run an automation when a comment is added, trying to sync that comment to a db.
Hey,
So, atm we have activity event emitted but not stored.
Cretaing/updating/deleting activities triggers an event, but this event is not stored in the database - it is just emitted over websockets to notify connected listeners.
with logger.contextualize(activity_id=activity_id, activity_type=activity_type):
await EventStream.dispatch(
"activity.created",
project=project_name,
description=f"Created {activity_type} activity",
summary=summary,
store=False,
user=user_name,
sender=sender,
sender_type=sender_type,
)
and the available event types are
ActivityType = Literal[
"comment",
"watch",
"reviewable",
"status.change",
"assignee.add",
"assignee.remove",
"version.publish",
]
There are also these additional activity events
"entity.folder.status_changed": cls.handle_status_changed,
"entity.task.status_changed": cls.handle_status_changed,
"entity.version.status_changed": cls.handle_status_changed,
"entity.product.status_changed": cls.handle_status_changed,
"entity.task.assignees_changed": cls.handle_assignees_changed,
"entity.version.created": cls.handle_version_created,
I think updating the post title to reflect it’s about activity events would be better, what do you think?
ya i guess if its just an event or activity that i am able to capture it should be fine i guess, how do i get that activity? can you help with a boiler code?
Oh, there’s a new PR to log activites.
ynput:develop ← ynput:store-activity-events
opened 09:41AM - 02 Jun 25 UTC
This pull request introduces a mechanism to distinguish between activities that … should or should not be stored in the database, along with updates to event dispatch logic in several activity-related functions. The key changes include adding a `DO_NOT_TRACK_ACTIVITIES` set to specify activities excluded from database storage, modifying event payloads, and updating descriptions for dispatched events.
This PR allows comments to be handled by services
ah… awesome, i will wait for the next release
1 Like