During the last week we developed initial database scheme [TS-36] and wrote liquibase migrations [TS-39]. Also defined the backend architecture [TS-45] and created APIs for the services (RestAPI and gRPC): [TS-50], [TS-51], [TS-56], [TS-59]. Studied the SSO that we are using (Microsoft Entra ID) and described how to work with it at our team’s notion site. And the last one - started the development of auth service [TS-59].

During the week we faced some problems, related to overall architecture and contracts, but we spoke about it together and decided to do it how it done now. The biggest problem was about filtering recomentation that were calculated by ML services. It was not clear what services should do it and how (backend or ML services). We decided to leave that feature and return to it later, but anyways, during the discussion , there were some important notes and takes related to the problem and we will definitely return to them later!

Week 5

During this week, we have implemented several important features and improvements to the project management system:

1. Add Desired Team Size for Project Owners [TS-92] PR-76
   • Updated the database structure by adding a new field for specifying the desired team size during project creation.
   • Implemented a restriction: project owners cannot add more members to their team than the specified limit.
2. Change courseName Field to Entity Reference [TS-190] PR-68
   • Replaced the courseName string field in the project entity with a reference to the Course entity.
   • Now project owners can select a course from the existing list or create a new course if it doesn't exist in the system.
3. Add Exceptions for Project Applications [TS-186] PR-68
   • Added validation to prevent project owners from applying to their own projects.
4. Implement Application Deletion for Students [TS-178] PR-68
   • Students are now able to delete their own applications for projects.
5. Application Status Management for Project Owners [TS-89] PR-76
   • Added functionality allowing project owners to manage the status of applications to their projects.
   • Project owners can now accept or reject applications directly from the “My Projects” page.
6. Implement Application Review Interface for Project Owners [TS-88] PR-76
   • Created a feature where project owners can view applications to their projects in the form of applicant user profiles.
7. Implement Favourite Project logic [TS-90] PR-81
   • Now user can add project to favourites, delete it from that list, and view their favourite projects.

Also, in collaboration with our frontend developer, we updated the project application response format [TS-196] PR-71.

Далее может повторяться инфа, представленная сверху, просто для объяснения, зачем мы это сделали.

There were multiple clarifications and changes regarding how project-related data should be structured and returned in API responses. Additionally, a fix was applied to enforce a rule preventing project owners from adding more team members than the specified team size. Early on, this constraint was missing, and it was added after internal review and testing. On top of that, throughout the week, we maintained active communication with our frontend developer to quickly resolve integration mismatches, clarify endpoint behaviors, and adapt backend responses to frontend UI needs. This collaborative approach helped avoid potential blockers and ensured consistent progress on both sides.

Week 6

Features:

• Add project view tracking: Implemented click logic in the project details endpoint to track project views to improve AI recommendations [TS-246], PR-99.
• Team member removal by project owner: Added support for project owners to remove already accepted team members [TS-194], PR-86.
• Dynamic roles and skills filters: Filters now display only roles and skills that are actually used in existing projects [TS-213], PR-88.

Improvements: