Comment 2 for bug 1813096

Environment tested: Master
Browser tested: Chrome

PRECONDITIONS:
------------------------
1) UserA portfolio page exists
--- a) is public viewable
2) UserA group portfolio page exists
3) UserB exists to make a report of objectionable content
--- a) user has access to the group portfolio page

TEST STEPS:
------------------------
1) UserB browses to the publicly viewable portfolio page of UseA
2) UserB clicks the "Report objectionable material" link found under the ellipsis icon of the page
3) User clicks the cancel link in the modal
4) Confirm that modal window disappears ✔
5) Confirm link found under the ellipsis icon of the page displays the following "Report objectionable material" and is clickable ✔
6) UserB click the "Report objectionable material" link again
7) User fill in required complaint field and click the "Notify administrator" button
8) Refresh the page (F5)
9) Confirm that the Objectionable message is displayed at the top of the page ✔
--- a) message is " When a user browses to another users page and clicks the objectionable content link and then clicks cancel. The user is then unable to click the objectionable content link." ✔
--- b) User has selection of "Still objectionable " and "Not objectionable" ✔
10 ) Click the ellipsis icon for the page
11) Confirm that a link "Objectionable material reported" exists ✔
12) User browses to the Group portfolio page of UseA
13) Confirm the above script applies to the Group portfolio page ✔

Catalyst QA Approved ✔