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

OOO Status Tracking and ignoring Negligence tagging during ooo #2264

Open
6 of 10 tasks
prashant67690 opened this issue Nov 22, 2024 · 0 comments
Open
6 of 10 tasks

OOO Status Tracking and ignoring Negligence tagging during ooo #2264

prashant67690 opened this issue Nov 22, 2024 · 0 comments
Assignees

Comments

@prashant67690
Copy link

prashant67690 commented Nov 22, 2024

Issue Description

The OOO (Out of Office) Status Tracking with Approval System feature aims to streamline the process of managing developers' OOO requests, integrate an approval system, and improve task progress tracking during OOO periods. The system also ensures fair treatment of developers on OOO by exempting them from negligence tagging while providing updates through Discord notifications.

Expected Behavior

  • Developers can submit OOO requests that are reviewed and approved by authorized users (Super Users).
  • Approved OOO requests trigger a notification in a designated Discord channel, including details such as:
    • Developer's name.
    • Start and end dates of the OOO period.
    • A tag indicating "OOO - Out of Office."
  • Employees on OOO are exempt from negligence tagging for not updating task progress.
  • Upon returning, employees must resume regular task updates.
  • Super Users can reassign tasks if deadlines are at risk due to an employee's OOO status.

Current Behavior

  • Inefficiencies in managing OOO requests, leading to confusion and unfair tagging as negligent.
  • Employees on OOO may still be flagged for not updating tasks, causing unnecessary stress.
  • Task reassignments are manual and lack of clarity during OOO periods.

Screenshots

Reproducibility

  • This issue is reproducible.
  • This issue is not reproducible.

Steps to Reproduce

  1. Submit an OOO request.
  2. Approve or reject the request via the Super User interface.
  3. Observe the Discord notification and system behavior for negligence tagging.

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Additional Information

  • Role-based access will ensure only authorized users (Super Users) can approve/reject OOO requests.
  • The Discord notification system will use the Discord bot API to send updates in real time.
  • Data security measures, such as encryption, will be implemented to protect personal leave details.

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