Modifying a Project or Component Member with Admin Role Results in Unsolicited Change to a Component PoC

[christopher-m-hosmer]

The PoC should never change unless a member with the "Admin" role explicitly changes the "Component Details"

Setup

Start New Project -> Fill out form

• Project Title: value
• Project Description: value
• Visibility: discoverable
• Slack Channel ID: null

Create a New Component -> Fill out form

• Select a Security Requirements Guide: General Purpose Operating System Security Requirements Guide (V2R1)
• Name: value
• Version: value
• STIG ID Prefix: value
• Title: value
• Description: value
• Select PoC: set to the person that is creating the component (e.g. DOG)
• Slack Channel ID: null

Scenario 1

Open Component: PoC set to the person that created the component (e.g. DOG)
Navigate back to the Project and Select Members
New Member -> select e-mail address for user not yet in Project -> select "Admin" as role (e.g. CAT) -> "Add User to Project"

BUG > Navigate to Components: added member with "Admin" role is incorrectly added as the PoC for the existing component (e.g. CAT)

Scenario 2

Open Component -> Update Details -> change PoC back to the person that originally created the component (e.g. DOG) -> Update Details
Select "Members" while still in the Component
Click "New Member" -> select e-mail address for user not yet in Project or Component (e.g. RABBIT) -> select "Admin" as role

BUG > Navigate to Components: added member with "Admin" role is incorrectly added as the PoC for the existing component (e.g. RABBIT)

Scenario 3

Vulcan is still in the Project Member view -> "Remove" the just added Project member (e.g. RABBIT)

BUG > The last added Project member with "Admin" role is incorrectly added as the PoC for the existing component (e.g. CAT) instead of it going back to the last set PoC (e.g. DOG)