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

feat(MBI): Release MBI to develop #249

Merged
merged 116 commits into from
Jun 6, 2024
Merged

feat(MBI): Release MBI to develop #249

merged 116 commits into from
Jun 6, 2024

Conversation

dembA7
Copy link
Contributor

@dembA7 dembA7 commented Jun 6, 2024

MBI: Release to staging

[MBI]: Se liberan los cambios de MBI a la rama develop.

Descripción

Se agregaron los siguientes requisitos funcionales.

  • RF06 | Notificación de asignación de tarea
  • RF31 | Notificación entre áreas en un proyecto compartido
  • RF61 | Consultar Calendario de Google
  • RF13 | Eliminar Proyecto
  • RF23 | Eliminar Clientes
  • RF37 | Consultar historial de viáticos
  • RF29 | Crear un nuevo reporte de viático
  • RF32 | Consultar detalle de un reporte de viático
  • RF40 | Modificar estatus reporte de viáticos (administrador y personas específicas de contable)
  • RF35 | Eliminar reporte de viático
  • RF34 | Descargar reporte de viático

Cambios realizados

  • Se modificaron controladores, rutas, servicios, tests, repositorios, interfaces y mappers.
  • Se modificó el schema de prisma, y se añadieron migraciones.
  • Se añadió la librería Resend para el uso de correos.

Pruebas

Se construyeron las pruebas unitarias necesarias para comprobar el correcto funcionamiento de todos los requerimientos.

Screen de pruebas y/o notas

N/A

Daniel Hurtado and others added 30 commits May 22, 2024 22:55
Co-authored-by: Ramona Nájera Fuentes <RamonaNF@users.noreply.github.com>
Feat/Expenses/RF32: Endpoint for expenseReport data by id
fix(RF32): Add accounting role to access all expense reports
dembA7 and others added 21 commits June 3, 2024 12:20
This commit updates the sendProjectStatusUpdateNotification function in the NotificationService. It now includes a validation check to ensure that the sender is not from the same department as the recipient. If the sender is from the same department, the function returns a message indicating that an email cannot be sent to the same department. This helps prevent unnecessary notifications within the same department. The validation is performed by the new validateSenderDepartment function, which retrieves the employee and department information using the EmployeeRepository and DepartmentRepository respectively. If the validation fails, the function returns the appropriate error message. This enhancement improves the functionality and reliability of the sendProjectStatusUpdateNotification function.
…tre-areas

Feat/rf31 notificacion entre areas
…cessfully deleted, and an unnecessary line was deleted
…deViatico

Feat/rf35 eliminar reporte de viatico
@dembA7 dembA7 changed the title MBI Staging MBI Develop Jun 6, 2024
@dembA7 dembA7 merged commit cf80fbf into develop Jun 6, 2024
2 checks passed
@dembA7 dembA7 changed the title MBI Develop feat(MBI): Release MBI to develop Jun 8, 2024
Copy link
Contributor

@Ian326 Ian326 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 👍

Copy link
Contributor

@RamonaNF RamonaNF left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Revisado

Copy link
Contributor

@ArmandoRosasB ArmandoRosasB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bien

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 this pull request may close these issues.