Template:SmallCR: Difference between revisions

From Calidus HUB
(Added TemplateData)
(Added TemplateData)
 
Line 312: Line 312:
],
],
"description": "A (Approve), R (Reject) or D (Defer).",
"description": "A (Approve), R (Reject) or D (Defer).",
"type": "string"
"type": "string",
"suggestedvalues": [
" ",
"A",
"R",
"D"
]
},
},
"Justification": {
"Justification": {

Latest revision as of 14:54, 27 February 2026

Small Change Request (Analysis)

Project/Log Number: {{{Client}}} / {{{LogNumber}}}

Date: {{{Date}}}

Requested By: {{{Requester}}}

Prepared By: {{{YourName}}}


Change Category (SCE_WMS, CTMS, EPOD, PORTAL, etc):
{{{System}}}
 

Describe the Change Being Requested:
{{{Request}}}
 

Describe the Reason for the Change (new requirement, s/w fix, problem management etc):
{{{Reason}}}
 

Describe all Alternatives Considered:
{{{Alternatives}}}
 

List Program and Change Summary Required to Implement this Change:
{{{Changes}}}
 

Describe Risks to be Considered for this Change:
{{{Risks}}}
 

Estimate Dev/Test Effort (in days) Needed to Implement this Change:

SCR Analysis: {{{EST}}}
DEV: {{{DEV}}}
TEST: {{{TEST}}}

Describe the Implications to other Customers:
{{{Implications}}}
 

Requestor Sign off:

     
Approve
     
Reject
     
Defer

Justification of Approval, Rejection, or Deferral:
{{{Justification}}}
 


Usage

Method 1

  • Use the following page/section. Help:CreateNewPage#Create_Small_Change_Request
  • Click Create - you will be taken to your new page.
  • Enter the fields
    • Title should follow the conventions "SCR {Log} {Description}"
    • Always enter the client code and system.

Method 2

Create a new page and use the template as below.

{{SmallCR

|Client=The Supimix client code.

|LogNumber=The Supimix log number

|Date=The current date, in DD/MM/YYYY format

|Requester=The requester's name

|YourName=Your Name

|System=Change Category (SCE_WMS, CTMS, EPOD, Portal, etc)

|Request=Describe the Change Being Requested

|Reason=Describe the Reason for the Change (new requirement, s/w fix, problem management etc)

|Alternatives=Describe all Alternatives Considered

|Changes=List Program and Change Summary Required to Implement this Change

|Risks=Describe Risks to be Considered for this Change

|NO_COST=Include the cost section below (Y/N)

|EST=Estimate effort (in days) needed to implement this change

|DEV=Development effort (in days) needed to implement this change

|TEST=Testing effort (in days) needed to implement this change

|Implications=Describe the Implications to other Customers

|Status=The status, one of A (Approve), R (Reject) or D (Defer). Initially leave blank.

|Justification=Justification of Approval, Rejection, or Deferral

}}

Small Change Request (CR) template with support for both named and numbered parameters.

Template parameters

This template prefers block formatting of parameters.

ParameterDescriptionTypeStatus
Client CodeClient 1

The specific code identifying the client.

Stringrequired
Log/Call NumberLogNumber 2

The log, call, or DevOps reference number.

Stringrequired
DateDate 3

The current date in DD/MM/YYYY format.

Datesuggested
Requester NameRequester 4

The name of the person requesting the change.

Stringrequired
Your NameYourName 5

The name of the person completing this form.

Stringrequired
System/CategorySystem 6

Change Category (e.g., SCE_WMS, CTMS, EPOD, Portal).

Suggested values
CTMS EPOD MCS ASSIST TCM VEhub Vision WCS PORTAL WMS Bay Diary TOC
Stringrequired
Request DescriptionRequest 7

A description of the change being requested.

Contentrequired
Reason for ChangeReason 8

The business or technical reason for the change.

Contentrequired
Alternatives ConsideredAlternatives 9

Description of all alternatives considered.

Contentoptional
Change SummaryChanges 10

List Program and Change Summary Required.

Contentrequired
RisksRisks 11

Describe Risks to be Considered for this Change.

Contentrequired
Exclude Cost SectionNO_COST 12

Include the cost section below (Y/N).

Suggested values
Y N
Default
N
Stringrequired
Estimate EffortEST 13

Estimate effort (in days) needed.

Numberoptional
Development EffortDEV 14

Development effort (in days) needed.

Numberoptional
Testing EffortTEST 15

Testing effort (in days) needed.

Numberoptional
ImplicationsImplications 16

Describe the Implications to other Customers.

Contentrequired
StatusStatus 17

A (Approve), R (Reject) or D (Defer).

Suggested values
A R D
Stringoptional
JustificationJustification 18

Justification of Approval, Rejection, or Deferral.

Contentoptional