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

Implement User Attribution for Task Progress Updates #1280

Closed
6 of 10 tasks
AnujChhikara opened this issue Nov 8, 2024 · 0 comments · Fixed by #1292
Closed
6 of 10 tasks

Implement User Attribution for Task Progress Updates #1280

AnujChhikara opened this issue Nov 8, 2024 · 0 comments · Fixed by #1292
Assignees

Comments

@AnujChhikara
Copy link
Contributor

Issue Description

Currently, our task detail page allows any user to update the progress of a task, which is helpful in cases where a team member is unavailable, for instance, due to illness. However, we do not currently track who updates the progress. This can lead to confusion or misuse if someone writes inappropriate or incorrect information on behalf of another person.

Expected Behavior

Each time a task progress is updated, the UI should display the name of the user who made the update that is clickable link to their profile. This will ensure transparency and accountability for task progress updates.

Current Behavior

At present, when a task's progress is updated, there is no indication of who made the change. Users cannot easily see whether the person who updated the task is the original assignee or someone else.

Screenshots

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Navigate to the task detail page.
  2. Observe the task progress section where updates are displayed.
  3. Notice that there is no indication of who updated 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