Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

1. Requirements

  • This phase is only focusing on the UCPath project. At a later phase we will include other project. 

  • SN Incident to TnT Jira "Defect" Issue Type

    • SN Incident will feed into TnT Jira "Defects" issue type upon creation.

      • All defects created for an incident must have "Does this apply to production" defaulted to 'YES'.

      • The "Affect's Version's" and "Fix Version's" fields must have "Production - Maintenance" defaulted in the defect.

      • The "Defected in Environment" must have "UCPHRPRD" defaulted in the defect.

      • Any attachments in the incident should be brought over into the defect.

      • Incident number must be brought over from SN to the Service Now ID field.

      • Required fields in TnT Jira when it's create are:

        • Initiator, Summary, Description, Detected in Environment, Affects Version's, Fix Version's, Business Unit, Component, "Pay, Benefit, or General Ledger Impacts?", Required?, # of Employees Impacted?, Impact on Manual Work/Costs? 

    • TnT Jira will feed into SN the defect number and any comments added into the defect.

    • TnT Jira will continue to feed updates to the SN incident until the defect is closed.

    • SN will continue to feed updates to TnT Jira defect until the incident is closed.

  • TnT Jira "Migration" Subtask to SN Change Request

    • Manually trigger a SN Change Request from the "Migration" sub-task in TnT Jira.

    • Include the following fields:

      • Reporter, Summary, Description, Migration ID, Parent Key number and Subtask Key number

    • Any attachments in the sub-task should be brought over into the SN Change Request.

2. Jira to ServiceNow[Comments + Attachments]

3. Jira to ServiceNow[ CR ]

  • Scope: Create

  • Summary : UCPath Migration - Migrate CSR {Migration ID}/ UCP-{Parent Key number} to PROD / {Subtask Key number}

  • Description:

UCPath Migration - Migrate CSR {Migration ID}/ UCP-{Parent Key number} to PROD / { Subtask Key number }

Reporter: { Name of the reporter}

Note: Any attachments in the sub-task should be brought over into the SN Change Request.

3.1 Field Mapping for CR

Sl No

ServiceNow Field

Jira

Value

Remarks

1

Number

(will be in callback)

(system assigned)

2

Parent

No

N/A

3

Requested by

Yes

(varies)

Need to ass the Ids

4

Configuration item

Yes

(varies)

Pass this “UCPHRPRD” and check if it works else pick the sysid of this name

5

Owner group

N/A

PeopleSoft Support Services

SysId: 329e8e485154950078c1717bfc16b68f

6

Impact

No

derived from Risk Assessment but since RA is boilerplate this will always have a value of "4 - Low"

7

Risk

No

derived from Risk Assessment but since RA is boilerplate this will always have a value of "3 - Medium"

8

Type

No

Out of scope, depends on lead time between generation of CR and deployment

Pass as”Normal”

9

Category

No

"Application"

10

Change Request State

No

As per spec, a change request record will be created and left in Draft status

11

Complexity

No

"Minor"

Set as” Minor”

12

Monitoring Changes

No

"No Changes Needed"

Pass as “No Changes Needed”

13

Other Reference Number 

Yes but analysis needed

NULL

14

Environments impacted

Yes but not used

"Production" (other environments are out of scope)

Pass as “Producation”

15

Approval Exception/Follow-up

No

NULL

16

Title/ Short Description

Yes (requires parsing)

UCPath Migration - Migrate CSR #### / UCP-##### to PROD

17

Description

Yes (requires parsing)

UCPath Migration - Migrate CSR #### / UCP-##### to PROD

UCPath Migration - Migrate CSR #### / UCP-##### to PROD
Requested By: sharmendra

Schedule

18

Planned start date

No

(out of scope)

For Now put random date less than end date

19

Planned end date

No

(out of scope)

For Now put random date greater than start date

20

Impact During Change

No

"No Downtime Expected"

Planning

22

Implementation Plan

No

"1. Verify CSR in STAT Tool and its dependencies

  1. Migrated the CSR as per the migration instruction document attached to the CSR

  2. Migration instructions may include archive set, DMS, menu components, security changes, SQR, SQC, COBOL, SQLs

  3. If migration includes COBOL program, request PSAdmin team to compile COBOL programs

  4. Compare the project between production and PUAT and address any discrepancies

  5. Attach all logs to the CSR

  6. Update Jira issue(s) to request production validation"

23

Justification

Yes (requires parsing)

"Copy the description from the JIRA UCP-YYYYY"

24

Pre Test Plan

No

"The Fix via STAT CSR has been validated in PTST/PUAT environment and has been documented in JIRA tool
Please refer the Defect in JIRA tool  for additional Testing details"

25

Post - Test Plan

No

"Release Team will run a compare report to ensure successful migration.   If the job fails they will troubleshoot, correct or contact developer for guidance.
ITSS will validate the fix in PROD after successful migration"

26

Backout Plan

No

"Before migration:
Project:

  1. In the app designer, please take a backup of the project mentioned in the CSR. Method: Copy Project to File

  2. Copy the folder to a backup folder,

File Objects:

  1. Take a backup of the files from prod and store it in a backup folder (Ex. SQRs, Cobols, HTML, Pdf..)

DMS Scripts:

  1. Take a backup of the data using either the Export DMS script or in consultation with the developer. When in doubt, please request the developer for additional instructions.

  2. Store the dat file in the backup folder and rename is as necessary.

Back out after Migration:
Project:

  1. Copy the project from file using the back up

  2. Build the project if necessary

File Objects:

  1. Copy the files from the backup

DMS Scripts:

  1. Run the import script using the backup dat file"

27

Impact

No

"UCPath Application is Impacted by this Change.
The Fix  will resolve the problem documented in the JIRA Tool and thereby ensuring smooth functioning of UCPath application"

References

  • No labels