Skip to content

Patch ServiceNow Planning Fields when creating a Standard Change Request #10160

Description

@grace-rehn

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your feature request, making sure it's handled appropriately.

Prerequisites

  • I have searched open and closed issues to make sure it isn't already requested
  • My team has started working on this issue
  • I have written a descriptive issue title

The enhancement

The Need

ServiceNow does not accept customer planning fields when creating a Standard Change request.

This blocks customers who want Standard Change's automatic approval but still need dynamic, per-deployment content.

Example of effected fields:

Octopus.ServiceNow.Field[description]
Octopus.ServiceNow.Field[implementation_plan]
Octopus.ServiceNow.Field[backout_plan]
Octopus.ServiceNow.Field[test_plan]

Solution

Patch these planning fields when creating a Standard Change request.

Important Note:

ServiceNow blocks changing these fields after a Standard Change has been created, via its built-in Restrict fields from Standard Change Business Rule.

If your ServiceNow instance still has this rule active (the default) and you set these Octopus.ServiceNow.Field[...] variables, Octopus's attempt to apply them will fail with an error from ServiceNow.

To use this feature, you'll need to adjust that Business Rule on your own ServiceNow instance (e.g. exempt Octopus's integration user from it) so the update is allowed. (Business Rule docs)

Screenshots and Mockups

Screenshot

Links

Metadata

Metadata

Assignees

Labels

kind/enhancementThis issue represents an enhancement we are committed to adding to Octopus as some time

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions