Update WPS (P2Pass CSP) project with new requriemetns - roybea2005/Jira GitHub Wiki

WPS project is taking another pass at the filed with Keith and they have some recommendations to change the various project attributes as listed in the ticket CTI-1013. Following are the details from the ticket.

Several enhancements to WPS Project are requested in this Change plus, the WPS project needs to be revised to all it to support tickets for both the CSP and P2PaaS platform. Originally , CSP tickets were going to be logged into CTI instance.

This change will stay in Queued status until all revisions are identified and then it will be submitted .

The following changes are needed in JSD DEV so can be tested by Platform Support teams:

Add new custom Field - Platform

Name = Platform

Type = Single Select list

Options = P2PaaS, CSP, Unknown

Field is optional

Add to these screens:
- Incident CREATE, VIEW, EDIT and Portal Screen
- Service Request CREATE, VIEW, EDIT and Portal Screen
- Change Request CREATE, VIEW, EDIT and Portal Screen
- Workflow screens for all Issue types:
  - Admin Update screens
  - Update Completion Data screen
  - Screens that appear with issue is Resolved/Completed or Cancelled
  - Change Submit Screen
Set Default for Assignment Group field in context for WPS to be WPS-Ops
In WPS, Change the columns shown for all Queues to include the Platform field as last/right most column
In WPS, Change the shared Filters for WPS project to include the Platform field as last/right most column
Add a 2 dimensional table gadget to WPS Dashboard to show number of total tickets created in WPS variable 1 = Platform, variable 2 = Issue Type.

In WPS, add value options to these fields:

Account Name(s) -> Commerce Service Platform (CSP) - Internal

                                 IBM Digital Commerce (IDC) 

                                 Inventory Visibility (IV)  

                                 OMS Insights (OMSI)

                                 Store Inventory Manager (SIM)

Environment -> Development/Test

Category -> add option for Access Question

                    revise  Application Update to be   Platform Update

In JSD PROD ONLY ...Revise web hooks in place for all CSP Teams to also post to slack channel if project = WPS

Example: Webhook for DataServices for CTI

  a) Title changed to mention for CTI or WPS projects

  b) JQL changed

      from:    project = CTI and "Assignment Group" in (FS-DPaaS, CSP-DataServices)

     to:        project = CTI and "Assignment Group" in (FS-DPaaS, CSP-DataServices)  or  project = WPS and "Assignment Group" in (WPS-DataServices)

Edit the Assignment Group field context for WPS project and change order the values to match this order

 1.WPS-Ops

 2. WPS-L3-Container-Services

 3. WPS-DataService

 4. WPS-CoreServices

 5. WPS-Network

 6. WPS-Security

 7. WPS-Storage

 8. WPS-VMWare

 9. WPS-Systems

10. WPS-Jira-App-Support

Add Post-Function to add a label when the TRANSFER transition is used.

This already in place in JSD DEV so only needed in JSD PROD only for WPS Incident & Service Request workflow, add a post-function to the Transfer transition. Copy/Paste the post-function on JSD DEV for WPS Incident workflow that is called Add Transferred Label when transfer function is used to add the new post-function.
Add validator in WPS Change workflow to force Technical Approver to be required if assignment group is WPS-Network. For the Create and Submit for Approval transitions, add Simple Script type validator
```
 Name =  Require Technical Approver when WPS-Network Change

 Condition script = 
```

// If Issue is assigned to WPS Network ...

if ( cfValues["Assignment Group"]?.value == “WPS-Network ) { // ..Then check to ensure a Technical Approver was provided

if (cfValues["Technical Approvers"] == null)  {return false}

 else {return true}

}

else {return true}

    Error Msg:  Enter an ID in Technical Approvers.  This field must be provided for Network Team changes

    Field = Technical Approvers

Edit WPS Field Configuration for Incident, Service Request and Change to include the following:

 Priority Field  -  Edit the Description to say   "See https:// _____.____  for definition of Priorities.   Sev 1 should only be used if Incident type record that involves a Production system outage"

Assignment Group Field -   Edit the description to say  "See https:// ___.____ for help in determining which Assignment Group to select.   If unsure, select WPS-Ops

Assignee field -   Edit the Description to say.     Select person to be assigned ticket.  Offering teams should leave this field set to Automatic so Platform teams can determine Assignee.

Change Type -  Edit the Description to say .  See https:// ___.__  for the definitions of Change Type.

Remove 'Major Application' as a value option for the Change Reason field.
Edit Options for Outage Reason field and remove the word Established from the options. So the new options would be

No Outage/ No Service Disruption
Outage or Service Disruption During the Maintenance Window for this Solution
Outage or Service Disruption Extending Beyond the Maintenance Window for this Solution
Outage or Service Disruption Outside the Maintenance Window for this Solution

DRAFT — Make Technical Approvers a required field on Change Requests. Edit the field configuration for WPS Change Issue type and make Technical Approvers a required field. IF THIS ONE IS IMPLEMENTED can delete #10 (req'd for WPS-Network)

NOTES:

The CSP & FS Queues will remain in the CTI instance and past and open CSP/FS tickets will remain in CTI. When all open issues for CSP & FS groups are closed the queues can be removed.
Tony will submit a bulk ID request to add everyone that is in a CSP Group to be in corresponding WPS Group (including Agents, Approvers, Contributors, Portal Users)
This change is just to prep the WPS project to support CSP, the CSP Assignment Group should remain active in CTI at this time. Whenever CSP changes from CTI to WPS project, the CSP & FS Assignment Groups should be disabled on the CTI instance so no new Issues can be opened. A separate change will be created for that event.