2013-04-05 Release

Summary

  • primarily indcident, request defect fixes for level setting of test cases
  • latent tweaks to unpublished catalog items in development
  • latent START replacement foundational work

Current Status Board

(if you can see this message, your browser probably sucks)

Progression

Status

Activity

Description

Duration

(tick)

Submit change request

Open a build/test change request in https://yale.service-now.com/, assign to INF SN App Support

minutes

(tick)

Schedule code review (Mon 1pm)

this should happen after initial handover and before release

minutes

(tick)

Build phase work

Begin work in dev

days

(tick)

Unit tests

Ensure all pushed to tst & unit tested

hours

(tick)

Initial code freeze

Hand over initial requirements list for functional & QA validation in tst

minutes

(error) canceled due to conflict

Conduct code review

Shouldn't take long, just basic validation of approach and docs

hours

(tick)

Defect fixes

Iterative follow-up work in dev, test for defect resolution

days

(tick)

Finalize release

Identify changes & updates that are going/not going. Push to (tst).

hours

(tick)

Final code freeze

Hand over final requirements list for functional & QA validation, w/ regression, in (tst)

minutes

(tick)

Go/no-go

Decide to push to production.

minutes

(tick)

Production deployment

Push to prd.

hours

()

Production rollback

If applicable; follow ServiceNow Rollback Procedure.

hours

()

Clone

clone from prd to: pre, trn, and tst for after release

hours

()

Notify stakeholders

send out email w/ summary status & link to release documentation, close out RFC and cancel clone requests, if rollback or no-go.

minutes

()

Target/Actuals

Deliver target/actuals using estimator spreadsheet or equivalent

hours

Change Control

CHG0006072

Release Notes

https://yale.service-now.com/kb_view.do?sysparm_article=KB0000066

Documentation

Detail is provided in the description. Full implementation detail is captured in the update set, which can be viewed (with admin rights) by drilling down into the links.

Requirements/Defects
Approved Updates

Update Set__(Original Names)___

Description

2013/04/04 - 1

Defect 469 - Incident: reopen notification not received by mgr, team leads

2013/04/04 - 1

Defect 469 - Incident: reopen notification not received by mgr, team leads

2013/04/06 - 1

Defect 420 - Incident: priority 1 incident scroller on IT homepage has wrong query - invalid. Must escape ampersand as well.

2013/04/06 - 1

Defect 420 - Incident: priority 1 incident scroller on IT homepage has wrong query - invalid. Must escape ampersand as well.

2013/04/04 - 2

START 77 - PTAEO point backend SOAP at webmethods PRODUCTION instance.

2013/04/03 - 2

Defect 465 - Request: SSG Enhancement Request fixes: limit ROM field to 10 chars, put client team field after dept. field.

2013/04/01 - 4

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values, some incidents with illegal priority (6,7)
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?
Also, some incidents have (unrelated) priority statements in the body which are being parsed by the inbound action - this should be disabled."

2013/04/01 - 3

"Defect 459 - Request: ""Propose a New Service Request Type"" request is not rendering fields properly in the RITM/SC Task

  • added all fields to the task carryover lists"

2013/04/01 - 2

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?

https://yaledevelopment.service-now.com/sc_task_list.do?sysparm_query=state!%3D3%5EORstate%3DNULL%5Estate!%3D1%5EORstate%3DNULL%5Estate!%3D2%5EORstate%3DNULL

Thanks"

2013/03/26 - 1

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?

https://yaledevelopment.service-now.com/sc_task_list.do?sysparm_query=state!%3D3%5EORstate%3DNULL%5Estate!%3D1%5EORstate%3DNULL%5Estate!%3D2%5EORstate%3DNULL

Thanks"

2013/04/04 - 2

START 77 - PTAEO point backend SOAP at webmethods PRODUCTION instance.

2013/04/03 - 2

Defect 465 - Request: SSG Enhancement Request fixes: limit ROM field to 10 chars, put client team field after dept. field.

2013/04/01 - 4

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values, some incidents with illegal priority (6,7)
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?
Also, some incidents have (unrelated) priority statements in the body which are being parsed by the inbound action - this should be disabled."

2013/04/01 - 3

"Defect 459 - Request: ""Propose a New Service Request Type"" request is not rendering fields properly in the RITM/SC Task

  • added all fields to the task carryover lists"

2013/04/01 - 2

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?

https://yaledevelopment.service-now.com/sc_task_list.do?sysparm_query=state!%3D3%5EORstate%3DNULL%5Estate!%3D1%5EORstate%3DNULL%5Estate!%3D2%5EORstate%3DNULL

Thanks"

2013/03/26 - 1

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?

https://yaledevelopment.service-now.com/sc_task_list.do?sysparm_query=state!%3D3%5EORstate%3DNULL%5Estate!%3D1%5EORstate%3DNULL%5Estate!%3D2%5EORstate%3DNULL

Thanks"

Manual Updates
  • D459 - manual fixup of assignment group in workflow, add wireframe_container field manually (doesn't carry over)