Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect Calculation of Missed Updates for Assigned Tasks on Progress Update Page #1190

Open
4 of 10 tasks
sahsisunny opened this issue Apr 7, 2024 · 0 comments
Open
4 of 10 tasks

Comments

@sahsisunny
Copy link
Member

sahsisunny commented Apr 7, 2024

Issue Description

The progress update calculation for assigned tasks on https://status.realdevsquad.com/tasks/PuTAvuWa7LLaToYejn09 is showing incorrect values for missed updates, leading to a display of 107 missing updates, which is inaccurate.

Expected Behavior

The progress update calculation should accurately reflect the number of missed updates based on the last update by the user and the assigned task's frequency of updates.

Current Behavior

The current behavior is displaying incorrect values for missed updates, resulting in 107 missing updates being shown when it should be a different value based on the last update and assignment details.

Screenshots

image

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Navigate to https://status.realdevsquad.com/progress/PuTAvuWa7LLaToYejn09?dev=true
  2. Observe the displayed number of missing updates (107)

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Additional Information

The calculation for missed updates needs to consider the last update made by the user and the task's update frequency to accurately reflect the number of missed updates.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant