Weight timeline implementation logic

[tkhahns]

What is the purpose of these statistics if they are from two different people? I guess more logic should be applied. For instance, statistics for unique customers A and B, where height and weight can change, not GENDER!

Last few records...

      Height: 1.0cm
      Weight: 55.0kg
      Gender: female
      Age: 11
      Health Goal: STEADY_STATE
      Ideal Daily Caloric Intake: 1002.0
      Recorded at: 2024-11-15 17:15:14
      Is able to see special chars: false

      Height: 178.11cm
      Weight: 78.0kg
      Gender: male
      Age: 20
      Health Goal: WEIGHT_LOSS
      Ideal Daily Caloric Intake: 1687.0
      Recorded at: 2024-11-15 16:30:18
      Is able to see special chars: true

weight timeline
Weight Timeline
 78.0 |  *
 76.9 |  *
 75.7 |  *
 74.6 |  *
 73.4 |  *
 72.3 |  *
 71.1 |  *
 70.0 |  *
 68.8 |  *
 67.7 |  *
 66.5 |  *
 65.4 |  *
 64.2 |  *
 63.1 |  *
 61.9 |  *
 60.8 |  *
 59.6 |  *
 58.5 |  *
 57.3 |  *
 56.2 |  *
 55.0 |  *     *
       ----- -----
       11-15 11-15

[soc-se-bot]

Team's Response

We refrain from becoming entangled in any political discussion about whether an individual can switch their gender or not. But, by implicitly forcing users to stick to one gender all the time, this is exactly what we would do (besides making a fraction of the world's population feel discriminated).

Instead, we designed HealthMate to be a companion for everybody. No matter their gender or weight fluctuations. Especially since the ability to switch one's gender does by no means endanger the system's functionality in any way.

Therefore, we give our users the maximal flexibility for entering and updating their user profiles in whichever way they want. The issue with having the ability to change the user's gender is unclear. Furthermore, Healthmate is only designed to be used by one user as per the constraints of the project.

Items for the Tester to Verify

:question: Issue response

Team chose [response.IssueUnclear]

• [x] I disagree

Reason for disagreement: The confusion of users' details, which I stated, is quite clear and straightforward.

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** It is a valid point that the users' details changing "does by no means endanger the system's functionality in any way". However, consider this a **Low Severity FeatureFlaw**. VeryLow Severity should only apply for cases that might affect the application's aesthetics, but this one might go against the program logic already.

---