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

[UX] Improve the Progress Update Flow #1274

Open
6 of 10 tasks
shubhdevelop opened this issue Oct 19, 2024 · 0 comments · May be fixed by #1290
Open
6 of 10 tasks

[UX] Improve the Progress Update Flow #1274

shubhdevelop opened this issue Oct 19, 2024 · 0 comments · May be fixed by #1290

Comments

@shubhdevelop
Copy link

Issue Description

The Current Implementation of the progress update is such that the user can update progress through the “progress bar” and “update progress” button without changing the task status into inProgress. Also, any user with an active task can update the progress using the “progress bar” without giving any task updates using the “update progress” button. It raises an issue that knowingly or unknowingly people miss on giving their task updates while updating the task progress.

Expected Behavior

People must give a Task update before update the progress(%).
And Could only update it if the task status has moved to inProgress

Current Behavior

People can update the progress(%) without giving task updates and
even when the task's Status is Assigned, and not In Progress

Screenshots

image

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Go to Status Site > my task > click on a in progress task
  2. click on the update text beside progress slider and change the progress
  3. The onChange event on the slider updates the task progress.

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.
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

Successfully merging a pull request may close this issue.

1 participant