nus-cs2103-AY2425S1 / pe-dev-response

0 stars 0 forks source link

Same entries for applications with slightly differing dates but completely different status. User may be confused about status of final internship application #2041

Open nus-se-script opened 1 week ago

nus-se-script commented 1 week ago

Screenshot 2024-11-15 at 4.41.16 PM.png

Steps to reproduce.

  1. add multiple entries with 3 different dates, each differing only by one day.
  2. Edit the status of each of the 3 to be different.

If I were a user looking at the image, I would be confused to which why there are 3 same applications with different outcomes. Each application is exactly the same except for the fact that the status is different. Does not cater well to be as a student who still needs to manage and sort out which is the final internship application outcome.


[original: nus-cs2103-AY2425S1/pe-interim#2802] [original labels: severity.Medium type.FeatureFlaw]

ZweZeya commented 1 week ago

Team's Response

We reject this for the following reason(s):

  1. Given two internship applications with the same Company Name, Email and Role but different Date, we do not consider these as duplicates. This is an intended behaviour as the user may want to apply for the same role in the same company but for different cycles. This aligns with the current internship landscape as companies hire interns across different cycles. For example, Govtech has multiple hiring cycles a year and the user may apply for multiple cycles resulting in different outcomes (i.e. rejected for the first cycle but accepted in the second cycle).
  2. If the user did apply for the same role in the same company for multiple cycles, we support the find and sort features where the user can filter by the company name and sort to have the most recent application appear in the first index. He can, therefore, refer to the most recent internship application for the latest/final status.

Note: We have put this issue to Low because this does not appear to be an inconvenience to the user as it is an intended behaviour.

Duplicate status (if any):

--