Technical task
While doing API request GET /tasks I noticed the following:
INSERT 1 task: Cancelled task_id: 1678542320 WARNING: task 1678542320 is finished but is missing 'completed_on' timestamp! INSERT 1 task: Cancelled task_id: 1678542517 WARNING: task 1678542517 is finished but is missing 'completed_on' timestamp! INSERT 1 task: Cancelled task_id: 1678542516 WARNING: task 1678542516 is finished but is missing 'completed_on' timestamp! INSERT 1 task: Cancelled task_id: 1678542514 WARNING: task 1678542514 is finished but is missing 'completed_on' timestamp! INSERT 1 task: Cancelled task_id: 1678542512 WARNING: task 1678542512 is finished but is missing 'completed_on' timestamp! INSERT 1 task: Cancelled task_id: 1678542515 WARNING: task 1678542515 is finished but is missing 'completed_on' timestamp! INSERT 1 task: Cancelled task_id: 1678542513 WARNING: task 1678542513 is finished but is missing 'completed_on' timestamp! INSERT 1 task: Cancelled task_id: 1678542511 WARNING: task 1678542511 is finished but is missing 'completed_on' timestamp!
The completed_on timestamp should never be missing from any task or workitem, unless it is still ongoing. Would it make sense to set it to reserved value, or even to the same timestamp as started on?
- resulted from
-
COIN-819 Implement GET tasks, taskDetails and workItemDetails APIs
-
- Closed
-