[PE-D][Tester C] Edit Command Allows Creation of Duplicate Organizations with Same Name

[soc-pe-bot]

Title: Edit Command Allows Creation of Duplicate Organizations with the Same Name

Description:
While using the application, I encountered an issue with the edit command, which allows the creation of two organizations with the same name. This behavior is unexpected and not documented in the User Guide.

Details:

Steps to Reproduce:

1. Open the application with default jar values.
2. Enter the command: edit 2 --name Alex Yeoh Inc. followed by pressing Enter.

Expected Behavior:
The application should not allow the creation of a new organization with the same name as an existing one, and it should provide an error message or prevent the creation of a duplicate organization.

Actual Behavior:
The edit command successfully creates a new organization with the name "Alex Yeoh Inc." even if an organization with the same name already exists.

Severity/Type Label:
This issue can be categorized as a high severity bug, as it allows for the creation of duplicate organizations with the same name, which can lead to confusion and data integrity problems.

I would like to emphasize that this issue might lead to unexpected results for users who assume that organization names are unique by default. It's possible that this behavior is unintentional, and the User Guide does not provide clarification on the role of the ID as a unique identifier.

Suggestion for Improvement:
To resolve this issue, it would be helpful to ensure that the edit command enforces the uniqueness of organization names and provides clear documentation in the User Guide regarding the uniqueness criteria, possibly by mentioning the role of the ID as a unique identifier. This will prevent the unintended creation of duplicate organizations and enhance the user experience.

---

Labels: severity.High type.FunctionalityBug
original: eyelessrhyme7/ped#2

[wxwern]

Out of scope - we allow duplicate names and only enforce unique IDs. A system to ensure this is not a user error would be a warning as per #140. For now, documentation should be updated to reflect this.