Versions Compared

Version Old Version 9 New Version Current
Changes made by

Sharmendra Vishwakarma

Sharmendra Vishwakarma

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

1. Problem Statement

In Service Now (SN) Incidents are reviewed by ITSS to determine if they are defects and need to be worked on by application development team, if determined that a fix  is needed the defect gets created into Tnt Jira and tracked in both places until the fix is moved into production. In addition, when the fix has to be moved into production, a Service Now Change Request is created to get the fix moved in production.  Updates are also tracked in both places until this ticket is closed out.

...

  • When any data push is failed from ServiceNow to Jira send e-mail to specific user group. This is application from both Defects and migration-subtasksub task

  • Make the sys-id as non-editable field in Jira

  • As an end user, I should be able to pull all the comments and attachments when CR is created for the first time.

  • As an ed user, I should be able to push description updates of migration sub-task to servicenow

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 pss the Ids

4

Configuration item

Yes

UCPHRPRD (in Jira as "Promote to" field value in migration subtask)

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

Component

needs dev work

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

Migration Request Date

Jira's "migration request date" plus 7:30 PM Pacific 

For Now put random date less than end date

19

Planned end date

Migration Request Date

Jira's "migration request date" plus 10:30 PM Pacific 

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"

...