Multiple Roles Should be Considered Acceptable

[jian7490]

Considering the value proposition stated in UG, this app should allow a person to have multiple roles, for example, to be both donor and volunteer, but this is not allowed in this app now.

[soc-pe-bot]

Team's Response

No details provided by team.

The 'Original' Bug

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

One person cannot have multiple roles

To recreate this: add r/donor r/volunteer n/name p/91234567 e/john@gmail.com a/Jurong

One person cannot have multiple roles. However, in real life, volunteers may also be donors and vice versa. I also cannot add someone again due to the duplication detection feature, so I cannot bypass this.

---

_{[original: nus-cs2103-AY2425S1/pe-interim#2712] [original labels: severity.Medium type.FeatureFlaw]}

Their Response to the 'Original' Bug

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

Thanks for pointing this out. However, we believe this issue is not in scope for the current iteration for the following reasons:

UG explanation is clear: It has been expressed clearly in UG that only one role is accepted for a person:

Format: add [r/ROLE] n/NAME p/PHONE_NUMBER...

multiple values can be provided for a field only when it is followed by a ..., e.g. [t/TAG]…​

Low Priority Use Case: This is a rare scenario that is unlikely to affect the majority of use cases, especially for small NGO administrators that we are targeting. Our current iteration prioritizes core functionalities that align with the app's main purpose.

Workaround Available: Users can achieve the same functionality by creating separate entries, such as Name donor and Name volunteer, for cases where multiple roles are needed. While separate tracking may involve additional effort, it is important to note that the primary focus of the app is to manage and track the various roles NGOs deal with, enabling them to exploit potential value effectively. It is not designed to function high-level identity management system, such as those used by governments, but rather as a role-tracking tool tailored to the needs of NGOs. We believe this is a reasonable compromise to ensure simplicity and to align with the app's core purpose: the effective management and utilization of different roles.

Focus on Core Features: The current development cycle prioritizes refining key functionalities and addressing high-impact use cases. While supporting multiple roles for a single person is a valid improvement, it is currently considered NotInScope because its implementation would require significant effort (field validation and retrieving role-unique fields become more complicated if multiple roles are supported), diverting resources from higher-priority tasks. The current design effectively handles the primary use cases, and this enhancement can be deferred to a future iteration when resources can be better allocated to its development.

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`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---