The feed is the activity log of a project. It provides a complete, chronological record of changes, comments, and system events within the project, giving every team member a overview of the project history at any time.
The feed is displayed as a widget on the project overview page and can be freely resized and repositioned there like any other widget.
What does the feed record?
The feed automatically captures all relevant activity in the project, including:
- Changes to project master data (e.g. title, project lead, start/end date, status)
- Creating, editing, and deleting tasks and subtasks
- Task status changes, including approvals and rejected approvals
- Assignment of people to tasks
- Publishing and deleting status reports
- Adding and removing files
- Comments and @mentions in tasks and status reports
- Changes to flavors at project and task level
- Color markings and status assignments of columns in the list view
Note
Status reports deleted by admins are also recorded in the feed.
Comments in the feed
Comments from tasks and status reports automatically appear in the project feed as well. This means all communication is visible in one central place – without having to open each individual task.
Using @mentions, team members can be directly notified about specific content. The mentioned person receives an in-app notification and optionally an email notification.
Internal comments
Comments can be marked as internal comments. Internal comments are not visible to guests in the project – neither in the task nor in the feed.
How it works:
- Open a task and navigate to the comment area.
- Write your comment.
- Activate the
Internal commentcheckbox before sending.
The comment will then be flagged with a corresponding indicator in the feed and in the task, and will not be visible to guests anywhere in the system.
Important
If an internal comment is replied to or quoted, the reply is automatically kept internal as well. This setting cannot be manually overridden.
Hiding people from the feed
When the API is used extensively, a large volume of automated actions can flood the activity log and make it difficult to find activity from real users. To prevent this, specific users - typically technical API users - can be hidden from the feed via the workspace settings.
Note
Hidden users are not shown in the feed. However, their entries are not deleted - the full activity log is preserved. This setting applies to the entire workspace and affects all projects. It can only be configured by owners in the Admin Center.
Feed retention period
The feed displays activity from the past 3 months. Events older than 3 months are no longer shown directly in the feed. Instead, a message appears indicating that the activity is still accessible in the activity log of the respective task.
Restoring deleted tasks
Tasks that have been directly deleted can be restored via the feed within 14 days. To do so, locate the corresponding entry in the feed and use the restore option.
Important
Restoration only applies to tasks that were deleted directly. If a folder is deleted, neither the folder itself nor any tasks it contained can be restored via the feed.
Note on archived and inactive projects
Note
The feed is fully preserved for archived projects and is available again in its entirety after reactivation.
For inactive projects, activities continue to be logged, but no notifications are triggered.
Feed as a widget
For information on how to add, configure, and position the feed widget on the overview page, see Widgets – Overview, Customization, and Use Cases.
API: Suppressing feed entries
When importing data via the API, feed entries can be controlled deliberately. Using the optional attribute noFeed="true", no individual change entries are created in the feed. Instead, only a summary message appears indicating that a certain number of elements were created.
Example:
<Tasks projectId="..." noFeed="true">
Tip
The noFeed attribute is particularly useful for large bulk imports where a high volume of feed entries would make it difficult to keep track of activity. The default value is false — without the attribute, all changes are logged in the feed as usual.
Comments
0 comments
Please sign in to leave a comment.