Body:

Description

When an Organization is deleted, the associated User accounts are not being deleted. This can lead to orphaned User accounts in the system that are associated with a non-existent Organization.

Expected Behavior

When an Organization is deleted, all associated User accounts should also be deleted.

Steps to Reproduce

1. Create an Organization.
2. Create a User associated with the Organization.
3. Delete the Organization.
4. The User account still exists in the system.

Description

In our current implementation of the models field of our model is defined as a CharField. This approach does not enforce the entry of valid URLs, potentially leading to data integrity issues if invalid URLs are stored. To enhance the robustness of our data validation and ensure that only valid URLs are stored in the website field, it is proposed to change the field type from CharField to URLField.

Proposed Changes

• Change the website field in the model from CharField to URLField.

Description

The functions department_for_organization and get_designation_for_department in views.py could be improved for better error handling and validation.

Also check if the user has access to the resources it's requesting.

Proposed Changes

• Remove the profile picture deletion logic from the Employee method.
• Implement a pre-delete signal receiver for the Employee model that checks if the employee has a profile picture and deletes it if it exists.

Issue

Some employee emails are not available, making it difficult to submit their details through the system.

ToDo

• Submission Without Email: Modify the employee details submission form to allow submission even if the employee's email is not available.

• Default Profile Pictures: Implement a feature to set default profile pictures for employees who do not upload their own profile pictures.

• Add Description Field: Include a description field in the employee profile to provide additional information, particularly useful for identifying the ward chairpersons and determining their respective wards.

Issues

• In organizations with identical department structures and designations, manually recreating them for each organization can be time-consuming and error-prone.

• Additionally, setting designation priorities can be confusing when no previous priorities are displayed.

Proposal

Cloning Departments and Designations:

• Introduce a feature to clone departments and designations from an existing organization to a new one.
• Provide an option in the administrative interface to select the organization from which to clone.

Enhanced Designation Priority UX:

• Improve the user experience for setting designation priorities by providing clearer guidance and context.
• When setting priorities, display existing priorities from similar organizations or defaults.
• Offer the option to auto-populate priorities based on predefined criteria or algorithms.

ToDo

• Implement Cloning Organization's Department and Designations
• Enhance Designation Priority User Experience

Title: Refactor admin.py for Employee and Organization and move form elements to forms.py

Description:

As part of our ongoing codebase cleanup and organization, we need to refactor the admin.py files for both the Employee and Organization models. The goal is to make the code more maintainable and easier to understand.

Tasks:

• Refactor admin.py for Employee: The EmployeeAdmin class in admin.py needs to be refactored. Any complex logic should be moved to model methods or utility functions.
• Refactor admin.py for Organization: Similar to Employee, the OrganizationAdmin class in admin.py also needs to be refactored.
• Move form elements to forms.py: Currently, some form elements and their logic are defined in admin.py. These should be moved to forms.py to separate the form presentation from the admin interface.

Issue:

Currently, profile pictures and logos can only be uploaded from local storage, which may limit users who prefer to use images hosted externally. This restricts flexibility and convenience in managing visual assets.

Proposal:

Introduce a feature to allow users to provide a URL for profile pictures and logos, enabling them to reference images hosted externally. This enhancement would offer users more flexibility in sourcing and managing visual assets for profiles and organizational branding.

ToDo

• Profile Picture on Employee
• Logo of Organization

Issue:

In organizations, certain designations may be intended for exclusive assignment to a single user, while others may be applicable to multiple users. However, the current system does not provide a way to differentiate between these scenarios, leading to potential confusion and mismanagement of designations.

Proposal

Introduce a new field in the designation settings to specify whether the designation can be assigned to multiple users within the organization. This enhancement will allow administrators to define the assignment behavior for each designation, ensuring clarity and consistency in role allocation.

ToDo

• Add a new field, such as "Allow Multiple Users," to the designation configuration interface.
• Modify the user assignment process to enforce the specified behavior based on the designation setting.