Actions48
- Main Card Actions
- Card Actions
- Attachment Actions
- Workspace Actions
- Board Actions
- Tag Actions
- Sticker Actions
- Document Actions
Card → Log Time
AI-generatedOverview
This node operation allows users to log time spent on a specific card within a project management or task tracking system. It is useful for tracking work duration on tasks, managing time allocation, and maintaining accurate records of time spent for reporting or billing purposes. For example, a user can log 3 hours spent on a card representing a development task on a given date with an optional comment.
Use Case Examples
- Logging 2 hours spent on a card for a feature implementation on 2024-06-01 with a comment 'Initial development work'
- Logging 30 minutes spent on a bug fix card on the current date without a comment
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card on which time is being logged. It ensures the time entry is associated with the correct task or item. |
| Time Unit | The unit of time for the duration being logged, such as minutes, hours, or days. |
| Duration | The amount of time spent on the card, expressed in the selected time unit. |
| Date | The date on which the time was logged. Time of day is not required, only the date. |
| Comment | An optional text comment to provide additional context or notes about the time logged. |
Output
JSON
card_id- The ID of the card on which time was logged.time_unit- The unit of time used for the logged duration.duration- The amount of time logged on the card.date- The date associated with the logged time entry.comment- Any optional comment provided with the time log entry.
Troubleshooting
- Ensure the Card ID is valid and corresponds to an existing card in the system; otherwise, the time log operation will fail.
- Verify that the duration is a positive number and the time unit is correctly selected to avoid invalid time entries.
- Make sure the date is in the correct format (yyyy-MM-dd) and is a valid calendar date.
- If the operation fails, check for network or API authentication issues if the node interacts with an external service.