You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current API for the task progress updates section in the task view page returns all updates at once. This can lead to performance issues and slow load times, especially when there are a large number of updates (e.g., 100+). Implementing pagination in the API will improve the efficiency and usability of this feature.
Expected Behavior
The API should return progress updates in a paginated format.
We can show only show a set number of progress update when page load. My suggestion - 5 .
The UI should seamlessly support pagination to fetch updates as the user navigates.
Current Behavior
The API currently returns all progress updates in a single response.
Screenshots
Reproducibility
This issue is reproducible
This issue is not reproducible
Steps to Reproduce
Navigate to the task view page.
Scroll down to the progress updates section.
Observe that all progress updates are loaded at once in the response.
Severity/Priority
Critical
High
Medium
Low
Additional Information
Checklist
I have read and followed the project's code of conduct.
I have searched for similar issues before creating this one.
I have provided all the necessary information to understand and reproduce the issue.
I am willing to contribute to the resolution of this issue.
The text was updated successfully, but these errors were encountered:
Issue Description
The current API for the task progress updates section in the task view page returns all updates at once. This can lead to performance issues and slow load times, especially when there are a large number of updates (e.g., 100+). Implementing pagination in the API will improve the efficiency and usability of this feature.
Expected Behavior
Current Behavior
Screenshots
Reproducibility
Steps to Reproduce
Severity/Priority
Additional Information
Checklist
The text was updated successfully, but these errors were encountered: