There is no way to differentiate between different planes of the same model

[praveenkrishna0512]

Brief description

• I can add multiple planes of the same model into Wingman. Thus, it would be good to have some way to differentiate between multiple planes of the same model. The only current workaround is to either remember to age of the plane or tag the model differently (ie B380-1, B380-2). However, I dont think either workarounds are ideal.

Steps to reproduce

• Switch to flight mode
• Enter add /m B380 /a 0
• Enter add /m B380 /a 360

Expected

• There should be a way to differentiate between both planes on the ground. If I look at two model B380, how will I know which one is 360 years old and which one is fresh D: The problem becomes worse if the planes have the same age.

Actual

• There is no way to differentiate between both planes

Screenshots

[nus-se-script]

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Hard to differentiate planes with same name in the location details

I have 2 planes with model "abc". However, if I were to unlink the plane, I need to remember which of the index I used to link it.

With more planes added, this can be a huge problem.

---

_{[original: nus-cs2103-AY2223S2/pe-interim#2925] [original labels: severity.Low type.FeatureFlaw]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Firstly, we should allow for two plane models with the same names, otherwise, this will be a significant feature flaw. Then the question is how to distinguish the two. Users could either use (1) the index of the plane, which is a unique identifier, or (2) the age of the plane, which is also unique in our program, just for the sake of distinguishing between planes with the same name.

Secondly, the root problem for this issue is that we only want to support so many characteristics of a plane. Currently, there are only two, so it's harder to distinguish. As we add more fields later on, this problem would be solved.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue response Team chose [`response.NotInScope`] - [x] I disagree **Reason for disagreement:** I believe that it is not hard to add another field for every plane, that is named `uid`, that stands for the unique identifier. This can then be tagged onto the end of the plane's displayed name in the Ui. Picture this -- an airline manager likely has at least 10 planes from each model, and they are likely bought at the same time. So the age is same and the plane model is same. _**According to your response, it is not even possible to add these planes, as the age must be unique. This is an even bigger Feature Flaw.**_ However, that aside, given that the ages are different, why must users be relying on a field named `age` to differentiate between planes? Furthermore, as the other bug report from the other team mentioned, once the plane is assigned to a location, there is no unique identifier attached to the model name. So I cannot even use the age to differentiate the planes once I have assigned them. I believe that there is no point in delivering upon other features, like having pilots, if airplane managers cannot differentiate between the numerous planes of the same models that they may posses and wish to assign to different locations/flights. The use case of the application comes under question.

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** > severity.Medium : A flaw that causes occasional inconvenience to some users but they can continue to use the product. I believe that this classification holds true for this bug. More explanation is given under the response for the dev team's _`Issue Response`_

---