[issue_tracker] update test plan (#8002)

Update test plan for issue tracker

Author: ridz1208

modules/issue_tracker/test/issue_tracker_test_plan.md

@@ -1,17 +1,17 @@
 # Issue Tracker Test Plan
 
 ## Issue Tracker Filter Form [Automation Testing]
-1. User can access the page only if they have `issue_tracker_reporter` or `issue_tracker_developer` permission
+1. User can access the page only if they have `Issue Tracker: Close/Edit/Re-assign/Comment on All Issues` or ` Issue Tracker: Create/Edit Own Issues and Comment on All Issues` permission
 2. User can see data from other sites only if they have `access_all_profiles` permission
 3. Test that all filters work. Nothing should be filtered at first loading.
-4. Test that all tabs (with filters) work and redirect to the correct table. 
+4. Test that all preset filters work and redirect to the correct table. 
 5. Test that the watching checkbox works correctly (issues that your userID is watching in issues_watching table)
 6. Check that links to issues in table are correct.
 7. Check that table sorts and displays additional pages correctly 
 8. Check that a user who does not have `access_all_profiles` permission and belongs to only one site can see all issues with a NULL centerID. Check that they have the label `All Sites` in the Site column. 
 
 ## Issue Tracker Create New Issue [Manual Testing]
-1. User can access the page if they have `issue_tracker_reporter` or `issue_tracker_developer` permission.
+1. User can access the page if they have `Issue Tracker: Close/Edit/Re-assign/Comment on All Issues` or `Issue Tracker: Create/Edit Own Issues and Comment on All Issues` permission.
 2. Check that title, assignee and site are required.
 3. Do not provide a PSCID value and set site to All Sites. This should set Site to NULL after success.
 4. Do not provide a PSCID value and and check that site can be populated by a particular site (except All Sites) in the dropdown values.
@@ -27,9 +27,9 @@
 
 ## Issue Tracker Edit Existing Issue [Manual Testing]
 1. User can access the page if they fulfill all the following conditions:
-	* they have `issue_tracker_developer` or `issue_tracker_reporter` permission 
+	* they have `Issue Tracker: Close/Edit/Re-assign/Comment on All Issues` or ` Issue Tracker: Create/Edit Own Issues and Comment on All Issues` permission 
 	* they have `access_all_profiles` or are a member of the site of the issue or the site has no issue.
-2. Users who have `issue_tracker_reporter` permission can edit all fields if it is their issue, but are blocked except for commenting and watching options for all other issues. Users with `issue_tracker_developer` permission can make all changes on all issues that they can view. 
+2. Users who have `Issue Tracker: Create/Edit Own Issues and Comment on All Issues` permission can edit all fields if it is their issue, but are blocked except for commenting and watching options for all other issues. Users with `Issue Tracker: Close/Edit/Re-assign/Comment on All Issues` permission can make all changes on all issues that they can view. 
 3. Users can only enter a PSCID for those candidate that are in their site.
 4. Submit invalid and valid PSCID and visit label pairs. Error messages should respond accordingly. Not that you cannot submit PSCIDs from other sites unless you have `access_all_profiles` permission
 5. Submit just a visit label - this should give an error message.
@@ -43,8 +43,8 @@
 
 ## Permissions [Automation Testing]
 1. Remove `access_all_profiles` permission.
-2. Remove `issue_tracker_reporter` permission
-3. Remove `issue_tracker_developer` permission
+2. Remove `Issue Tracker: Create/Edit Own Issues and Comment on All Issues` permission
+3. Remove `Issue Tracker: Close/Edit/Re-assign/Comment on All Issues` permission
 4. Test that the module behaves correctly as described above. 
 
 **Test the Issue Tracker Dashboard widget**