As I understand that keeping both old tag and new-tag name under a person is to avoid duplication, but it could cause inconvenience to user when they trying to update everyone in the existing tag to a new tag but he forgot that he already assigned the new tag to several contact.
For example:
Consider the user as a private tutor
He might want to name all the current student to ex-student after they all graduated. But he already add the new tag exstudent to the first student.
After renaming the tag, the contact 1 will still have the oldTag in the detail. Which may cause confusion if the user add in new contacts afterward for new intake of students but contact 1 is having both tag of students and exstudent. The user might be confused which is the correct tag.
This is a simple scenario to picture, but it may causes inconvenience if similar scenario happens.
It could have a work around, such as keeping only the newTag and remove the old one, or give a warning.
As I understand that keeping both old tag and new-tag name under a person is to avoid duplication, but it could cause inconvenience to user when they trying to update everyone in the existing tag to a new tag but he forgot that he already assigned the new tag to several contact.
For example: Consider the user as a private tutor He might want to name all the current student to ex-student after they all graduated. But he already add the new tag
exstudentto the first student.After renaming the tag, the contact 1 will still have the oldTag in the detail. Which may cause confusion if the user add in new contacts afterward for new intake of students but contact 1 is having both tag of students and exstudent. The user might be confused which is the correct tag.
This is a simple scenario to picture, but it may causes inconvenience if similar scenario happens.
It could have a work around, such as keeping only the newTag and remove the old one, or give a warning.
[original: nus-cs2103-AY2425S1/pe-interim#3986] [original labels: type.FeatureFlaw severity.Low]