{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":32098,"path":"it-service-management/devops-change-velocity/dev-ops-administration.md","title":"DevOps Change Velocity properties","bundle":null,"doc_type":null,"release":"australia","body":"\n# DevOps Change Velocity properties\n\nUse these properties to configure settings in the DevOps Change Velocity application.\n\nRole required: sn\\_devops.admin\n\nYou can view the properties from the DevOps Change workspace by navigating to **System configuration** > **Properties**.\n\nTo view the properties from the Classic UI, navigate to **All** > **DevOps** > **Administration** > **Properties**.\n\n\n
\n\nProperty\n\n\n\nDescription\n\n\n\nDefault\n\n\n\nName\n\n
\n\nMaximum retries for errored inbound events\n\n\n\nMaximum number of retries for errored inbound events.\n\n\n\n3\n\n\n\n\\[sn\\_devops.max\\_retry\\_count\\_inbound\\_event\\]\n\n
\n\nTool capabilities\n\n\n\nThe tool capabilities supported, entered as comma-separated values.\n\n\n\ncode,plan,orchestration,artifact,test\n\n\n\n\\[sn\\_devops.tool\\_capabilities\\]\n\n
\n\nDevOps change request approval text\n\n\n\nThe DevOps change request approval text to be used for change management customizations.\n\n\n\nApproved\n\n\n\n\\[sn\\_devops.change\\_request.approved\\_approval\\]\n\n
\n\nDevOps change request - Apply attributes on change creation\n\n\n\nIf enabled, change attributes are applied when a change is created. If there are any data policies applied on the change attributes, they are enforced when the change is created. If this property is not enabled, change attributes are applied after the change is created, which may cause change creation failure if any data policies are present on the change attributes.\n\n\n\nFalse \\(disabled\\)\n\n\n\n\\[sn\\_devops.change\\_request.apply\\_attributes\\_on\\_creation\\]\n\n
\n\nDuration of DevOps system health report \\(in days\\)\n\n\n\nDefaults to the last 7 days, to show system health metrics like inbound events.\n\n\n\n7\n\n\n\n\\[sn\\_devops.health\\_duration\\_report\\]\n\n
\n\nEnable automatic association of repos to apps on pipeline execution\n\n\n\nIf enabled, automatically associates repositories to apps and enables track when a pipeline identifies commits of a repository that is not yet associated. Also associates pipelines that are not yet associated to the corresponding app when the repository is already assigned to the app.\n\n\n\nYes \\(enabled\\)\n\n\n\n\\[sn\\_devops.enable\\_automatic\\_associations\\]\n\n
\n\nMaximum number of pages to process at a time for an import request\n\n\n\nThe maximum number of pages that must be processed at a time for an import request.\n\n\n\n10\n\n\n\n\\[sn\\_devops.import.max.pages.processing.per\\_import\\]\n\n
\n\nDevOps change request reusability decision subflow\n\n\n\nThe subflow that can be called to check if a previously created change can be reused, instead of creating a new one.\n\n\n\nsn\\_devops.change\\_request\\_reusability\\_subflow\n\n\n\n\\[sn\\_devops.change\\_request\\_reusability\\_decision\\]\n\n
\n\nGitHub URL\n\n\n\nFor GitHub, this field is used to get the API URL \\(for REST calls\\).\n\n\n\nhttps://github.com\n\n\n\n\\[sn\\_devops.github.url\\]\n\n
\n\nDevOps change request cancel state\n\n\n\nDevOps change request cancel state to be used for change management customizations.\n\n\n\n4 \\(Canceled\\)\n\n\n\n\\[sn\\_devops.change\\_request.cancel\\_state\\]\n\n
\n\nMaximum orchestration tool executions while importing\n\n\n\nMaximum orchestration tool executions while importing Jenkins freestyle jobs.\n\n\n\n1000\n\n\n\n\\[sn\\_devops.import.orchestration\\_tool.executions.maximum\\]\n\n
\n\nTo save payloads as attachments on the Import Request Page record, set the \"Value\" field to \"true\". Anything else is considered as false.\n\n\n\nIf true, the fetched JSON payload is saved as an attachment in the Import Request page.To save payloads as attachments on the Import Request Page record, set the **Value** field to true. Anything else is considered false.\n\n\n\nFalse \\(disabled\\)\n\n\n\n\\[sn\\_devops.import.save.payloads.as.attachments\\]\n\n
\n\nDevOps non-admin software quality summary flag\n\n\n\nEnable to view and monitor SonarQube scans configured on your GitHub Actions, Jenkins, or Azure DevOps pipelines as a non-admin SonarQube user.\n\n\n\nFalse \\(disabled\\)\n\n\n\n\\[sn\\_devops.non\\_admin\\_software\\_quality\\_summary\\_flag\\]\n\n
\n\nDefault test type\n\n\n\nDefault test type from orchestration pipelines.\n\n\n\nJUnit\n\n\n\n\\[sn\\_devops.default\\_test\\_type\\]\n\n
\n\nCoding tool branches per page\n\n\n\nNumber of coding tool branches per page.\n\n\n\n19\n\n\n\n\\[sn\\_devops.import.coding\\_tool.branches.per\\_page\\]\n\n
\n\nPlanning tool issues per page\n\n\n\nNumber of planning tool issues displayed per page.\n\n\n\n100\n\n\n\n\\[sn\\_devops.import.planning\\_tool.issues.per\\_page\\]\n\n
\n\nsn\\_devops role to be automatically added to active DevOps users\n\n\n\nThe sn\\_devops role entered in the value field is automatically added to users who are active DevOps users \\(for example, making a commit\\). If a role that is not in the sn\\_devops scope is provided, it is not added.\n\n Leave empty if no role should be automatically provided.\n\n\n\nsn\\_devops.viewer\n\n\n\n\\[sn\\_devops.discovered.user.auto.assign.role\\]\n\n
\n\nSoftware quality categories shown by default in the Pipeline UI view\n\n\n\nThe software quality categories shown by default in the Pipeline UI view, entered as comma-separated values.\n\n\n\ncoverage,lines\\_of\\_code,bugs,code\\_smells,duplications,vulnerabilities\n\n\n\n\\[sn\\_devops.sq\\_ui\\_category\\_preferences\\]\n\n
\n\nErrors or exceptions \\(comma separated\\) for which errorred inbound events are set to Retry\n\n\n\nErrors or exceptions for which the errored inbound events are set to Retry. Entered as comma-separated values.\n\n\n\nTimeOutException,FlowObjectAPIException\n\n\n\n\\[sn\\_devops.inbound\\_events\\_retry\\_error\\_list\\]\n\n
\n\nDevOps log level\n\n\n\nThe DevOps log level. Select the appropriate level from the following:\n\n- Error\n- Warning\n- Information\n- Debug\n- Trace\n\n\n\nWarning\n\n\n\nsn\\_devops.devops\\_log\\_level\n\n
\n\nCategorize DevOps change requests on **DevOps Change** field\n\n\n\n.Select this option to categorize change requests with category field set to DevOps as a DevOps change.\n\nClear to disable.\n\n\n\nFalse \\(disabled\\)\n\n\n\n\\[sn\\_devops.custom\\_change\\_categorization\\]\n\n
\n\nOrchestration tool executions per page\n\n\n\nNumber of orchestration tool executions per page.\n\n\n\n50\n\n\n\n\\[sn\\_devops.import.orchestration\\_tool.executions.per\\_page\\]\n\n
\n\nEnable import polling\n\n\n\nOption to enable polling of import requests. Clear to disable polling.\n\n\n\nFalse \\(disabled\\)\n\n\n\n\\[sn\\_devops.enable\\_import\\_polling\\]\n\n
\n\nGitHub API version path\n\n\n\nThe GitHub API version path.\n\n\n\n/api/v3\n\n\n\n\\[sn\\_devops.github.api\\_version\\_path\\]\n\n
\n\nTool permission check timeout per record \\(in milliseconds\\)\n\n\n\nDuring the tool connection process, the system performs permission validations in the foreground, and restricts the tool connection page. For every permission validation, a REST API call is made to external tools to evaluate the availability of the permission. The REST API response time may vary based on your network settings. To avoid delays, you can specify how long the system should wait to get a response from an external tool before marking the permission as an error through this property.\n\n\n\n10000\n\n\n\n\\[sn\\_devops.permission\\_check\\_timeout\\]\n\n
\n\nDevOps change request reusability model subflow\n\n\n\nThe DevOps change request reusability model subflow.\n\n\n\nsn\\_devops.devops\\_reused\\_model\\_change\\_request\n\n\n\n\\[sn\\_devops.devops\\_reused\\_model\\_change\\_request\\]\n\n
\n\nTime elapsed \\(in minutes\\)\n\n\n\nThe time elapsed in minutes. The retry job checks for errored inbound events from the time/value specified.\n\n\n\n1440 \\(7 days\\)\n\n\n\n\\[sn\\_devops.inbound\\_events\\_error\\_retry\\_mins\\_ago\\]\n\n
\n\nCancel the change request when the associated stage in the pipeline fails or is canceled\n\n\n\nWhen this property is enabled and the orchestration task mapped to a certain step in your DevOps pipeline fails or is canceled, the change request associated with that step is also canceled. A change request can be canceled only if it has not already been rejected or is not in the implement or review state at the time of cancellation.\n\n\n\nFalse \\(disabled\\)\n\n\n\n\\[sn\\_devops.cancel\\_change\\_on\\_pipeline\\_cancel\\]\n\n
\n\nCascade delete threshold \\(recommended foreground limit 1000\\)\n\n\n\nCascade delete threshold.\n\n\n\n1000\n\n\n\n\\[sn\\_devops.cascade\\_delete\\_threshold\\]\n\n
\n\nMaximum retries per page while importing\n\n\n\nMaximum retries allowed per page while importing data from tools.\n\n\n\n3\n\n\n\n\\[sn\\_devops.import.max.retries.per\\_page\\]\n\n
\n\nDevOps change request post implement state\n\n\n\nDevOps change request post implement state to be used for change management customizations.\n\n\n\n0 \\(Review\\)\n\n\n\n\\[sn\\_devops.change\\_request.post\\_implement\\_state\\]\n\n
\n\nDevOps change request implement state\n\n\n\nDevOps change request implement state to be used for change management customizations.\n\n\n\n-1 \\(Implement\\)\n\n\n\n\\[sn\\_devops.change\\_request.implement\\_state\\]\n\n
\n\nDefault committer score\n\n\n\nThe default committer score.\n\n\n\n50\n\n\n\n\\[sn\\_devops.committer.score.default\\]\n\n
\n\nEnable to track GitLab pull \\(merge\\) requests. If not enabled, then pull \\(merge\\) requests and related events will be ignored.\n\n\n\nWhen this property is enabled, GitLab pull \\(merge\\) requests are tracked in DevOps Change Velocity. If disabled, then all merge request events are ignored.\n\n\n\nYes \\(enabled\\)\n\n\n\nsn\\_devops.track.gitlab.pullrequests\n\n
\n\nDefault throttle reset time in minutes from current time\n\n\n\nIf a tool doesn't support a throttle reset time, the throttle reset time will be considered as the current time plus the value given for this property.\n\n\n\n15 minutes\n\n\n\n\\[sn\\_devops.throttle.reset.time.default\\]\n\n
\n\nEnable to track Azure DevOps Code Pull-Requests. If this is enabled then azure pull request web-hooks will be auto-configured when tool or project is configured.\n\n\n\nWhen this property is enabled, the Azure DevOps pull request web-hooks are auto-configured whenever a tool or project is configured.\n\n\n\nYes \\(enabled\\)\n\n\n\nsn\\_devops.track.azure.pullrequests\n\n
\n\nMultiply factor for committer score\n\n\n\nThe multiplication factor to be used for committer score.\n\n\n\n1\n\n\n\n\\[sn\\_devops.committer.score.multiply.factor\\]\n\n
\n\nAuto archive \\(in months\\)\n\n\n\nThe duration after which the table data is to be auto-archived.\n\n\n\n9\n\n\n\n\\[sn\\_devops.table\\_auto\\_archive\\_duration\\]\n\n
\n\nDeprecated - Enable debug flag \\(Use new property DevOps log level\\)\n\n\n\nDevOps Debug Logger.\n\n**Note:** This property is deprecated, use the **sn\\_devops.devops\\_log\\_level** \\(DevOps log level\\) property instead.\n\n\n\nYes \\(enabled\\)\n\n\n\n\\[sn\\_devops.enable\\_debug\\]\n\n
\n\nMaximum processing time per page while importing \\(in seconds\\)\n\n\n\nMaximum processing time in seconds, that should be allowed per page while importing data from tools.\n\n\n\n300\n\n\n\n\\[sn\\_devops.import.max.processing.time.seconds.per\\_page\\]\n\n
\n\nSupported webhook capabilities\n\n\n\nWebhook capabilities supported by DevOps Change Velocity.\n\n\n\ncode,plan,orchestration,artifact, test\n\n\n\n\\[sn\\_devops.supported\\_webhook\\_capabilities\\]\n\n
\n\nDevOps change request closed state\n\n\n\nDevOps change request closed state to be used for change management customizations.\n\n\n\n3\n\n\n\n\\[sn\\_devops.change\\_request.closed\\_state\\]\n\n
\n\nBulk flow timeout \\(in milliseconds\\)\n\n\n\nBulk flow timeout in milliseconds.\n\n\n\n60000\n\n\n\n\\[sn\\_devops.bulk\\_flow\\_timeout\\]\n\n
\n\nGitHub/Bitbucket coding tool commits per page\n\n\n\nNumber of coding tool commits per page for GitHub and Bitbucket.\n\n\n\n100\n\n\n\n\\[sn\\_devops.import.coding\\_tool.commits.per\\_page\\]\n\n
\n\nFolder depth\n\n\n\nRetrieves only those orchestration tasks and pipelines which are in folders whose nesting level is less than or equal to the number specified here. Folder Depth is the level of nesting done on folders in Jenkins, which contains the orchestration task and pipelines that you want to discover. For example, if you want to discover orchestration tasks and pipelines for a folder structure that is nested 2 times in your Jenkins environment, you must enter 2 as the value for this property.\n\n\n\n3\n\n\n\n\\[sn\\_devops.discover.jenkins.folder.depth\\]\n\n
\n\nDevOps change request handler subflow\n\n\n\nIf you are using a custom subflow instead of the Default Change Handler subflow in Flow Designer \\(which is used to populate the change request fields with default values\\), then you must update this property value to the new subflow. You can copy the Default Change Handler subflow in Flow Designer and update it according to your organization's needs. For information on the Default Change Handler subflow, see [Customizing DevOps flows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/devops-change-velocity/using-dev-ops-model-change-flow.md).For information on copying a subflow, see [Copy a subflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/copy-subflow.md).\n\n\n\nsn\\_devops.default\\_change\\_handler\\_subflow\n\n\n\n\\[sn\\_devops.change\\_request\\_handler\\_subflow\\]\n\n
\n\nCoding tool repositories per page\n\n\n\nThe number of repositories that must be displayed per page when you import repositories after connecting to a tool. The total number of repositories imported is not dependent on this property, but the number of repositories that must be displayed per page from the total number of repositories imported can be specified using this property. For example, if your tool contains 1000 repositories and you specify 100 as the property value, 1000 repositories will be imported of which 100 will be displayed per page in the Import Requests page.\n\n When you discover repositories, the number of repositories that must be retrieved per API call in the backend is also dependent on this property value. For a large number of repositories, set a relatively smaller value in this property so that lesser number of repositories are retrieved per call and the system does not time out.\n\n\n\n100\n\n\n\n\\[sn\\_devops.import.coding\\_tool.repos.per\\_page\\]\n\n
\n\nGitHub API URL\n\n\n\nGitHub API URL.\n\n\n\nhttps://api.github.com\n\n\n\n\\[sn\\_devops.github.api\\_url\\]\n\n
\n\nITBM Agile planning tool issues import max limit\n\n\n\nStrategic Portfolio Management \\(SPM\\) Agile planning tool issues import max limit.\n\n\n\n1000\n\n\n\n\\[sn\\_devops.import.planning\\_tool.itbm.issues.max.limit\\]\n\n
\n\nAssign a universal task and notify to update tool credentials when expired\n\n\n\nAdmins and tool owners will be notified \\(through universal task, email, banner, and field message\\) on expiry of tool credentials after the credentials have expired. As an admin or tool owner, you can update your tool credentials and connect the tool to prevent any further loss of data. For information on updating tool credentials, see [Update third-party tool credentials in DevOps Change Velocity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/devops-change-velocity/update-third-party-tool-credentials-in-devops-change-velocity.md).\n\n\n\nYes \\(enabled\\)\n\n\n\n\\[sn\\_devops.credential\\_expiration.notify\\_on\\_expiration\\]\n\n
\n\nNumber of days before tool credential expiry to assign a universal task and notify \\(if applicable\\)\n\n\n\nSet the number of days before tool credentials expiry to send notifications \\(through universal task, email, banner, and field message\\) to admins for GitHub tools created with basic authentication. To stop sending proactive notifications, select 0 as the value for this property. For information on updating tool credentials, see [Update third-party tool credentials in DevOps Change Velocity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/devops-change-velocity/update-third-party-tool-credentials-in-devops-change-velocity.md).\n\n\n\n3\n\n\n\n\\[sn\\_devops.credential\\_expiration.notify\\_before\\_days\\]\n\n
\n\nNumber of days to display warning alerts when events were not being received\n\n\n\nSet the number of days to display warning alerts in the **Last event received** field in the tool record when events were not being received. This only applies for tools which sends data to ServiceNow. The **Last event received** field in the tool record header and inside the tool record will be highlighted in yellow for warning alerts when the events were not being received.\n\n\n\n2\n\n\n\n\\[sn\\_devops.last\\_event\\_received.warning\\]\n\n
\n\nNumber of days to display critical alerts when events were not being received\n\n\n\nSet the number of days to display critical alerts in the Last event received field in the tool record when events were not being received. This only applies for tools which sends data to ServiceNow. The **Last event received** field in the tool record header and inside the tool record will be highlighted in red for critical alerts when the events were not being received.\n\n\n\n7\n\n\n\n\\[sn\\_devops.last\\_event\\_received.critical\\]\n\n
\n\nEnable whether Azure DevOps Run Commits must be determined from the last successful pipeline build\n\n\n\nIf enabled, DevOps Change will pick up the last commits, upto a maximum of 2000, created after the last successful pipeline build from Azure DevOps as part of Run Commits.\n\n If disabled, only the last 200 commits will be considered for Run Commits.\n\n\n\nNo\n\n\n\n\\[sn\\_devops.enable\\_ado\\_bulk\\_run\\_commits\\]\n\n
\n\nEnable whether GitHub Run Commits must be determined from the last successful workflow run\n\n\n\nIf enabled, DevOps Change will pick up the first 2000 commits after the last successful workflow run in GitHub as part of Run Commits.\n\n**Note:** Skipped commits are not considered.\n\n If disabled, only the last commit will be picked up for Run Commits.\n\n\n\nNo\n\n\n\n\\[sn\\_devops.enable\\_github\\_run\\_commits\\]\n\n
\n\nThis property decides whether to create a Generic Connection on configure operation for Azure DevOps\n\n\n\nThe step to enter the integration user name and password is required to configure webhooks when this property is enabled.\n\n\n\nNo\n\n\n\n\\[sn\\_devops.enable\\_ado\\_generic\\_connection\\]\n\n
\n\nMaximum limit for the number of pipelines that can be discovered for an Azure DevOps project\n\n\n\nSet the maximum number of pipelines that can be discovered in an import request for an ADO project. If your project has more than 15000 pipelines, then you can try setting this property value to that number and see if the pipelines get discovered. If not, you can reduce the value to a lower number and try to discover.\n\n\n\n15000\n\n\n\n\\[sn\\_devops.discover.max.pipelines.ado\\]\n\n
\n\nUpdate DevOps Change Request States Automatically when Change Receipt is Enabled\n\n\n\nUpdates the DevOps change request states automatically when change receipt is enabled. If you want to stop the automatic transition of the change request states even when change receipt is turned on, you must disable this property.\n\n\n\nSelected \\(enabled\\)\n\n\n\n\\[sn\\_devops.enable\\_change\\_receipt\\_state\\_transition\\]\n\n
\n\nSwitch to this user after token based authentication is successful\n\n\n\nIf the devops.system user is not available in your ServiceNow instance, use this property to set any other user that has the sn\\_devops.integration role, which is needed to complete the token authentication.\n\n\n\ndevops.system\n\n\n\n\\[sn\\_devops.token\\_auth.user\\]\n\n
\n\nMaximum limit for the number of times the discover action that exceeds the rate limit will be retried.\n\n\n\nDetermines the maximum number of times the discover action will be automatically retried after it reaches the rate limit. For example, if the rate interval in Azure DevOps is 5 mins, and you enter a value of 4 here, then after every 5min, the discover action will be retried for 4 times.\n\n\n\n10\n\n\n\n\\[sn\\_devops.max\\_retry\\_count\\_discover\\]\n\n
\n\nEnable change request creation even with errors in DevOps data retrieval\n\n\n\nIf enabled, when an error occurs in retrieving DevOps data like work items, commits, test summaries, security summaries, etc, the corresponding change request is still created. The data that can be retrieved will still be associated with the change request. For the data that cannot be retrieved, the reason for the error will be notified to the user in the third-party console, and the same information will also be added in the **Change Comments** field in the Step Execution record and the change **Worknotes**.\n\n\n\nNo \\(disabled\\)\n\n\n\n\\[sn\\_devops.enable\\_change\\_creation\\_with\\_partial\\_data\\]\n\n
\n\nEnable state transition from New to Assess when DevOps Change Request Manual Approval Flow is active\n\n\n\nIf enabled, updates the change request state from New to Assess directly when the DevOps Change Request Manual Approval Flow is active. If you want to stop the automatic transition of the change request state to Assess when the DevOps Change Request Manual Approval Flow is active, you must disable this property.\n\n\n\nYes \\(enabled\\)\n\n\n\n\\[sn\\_devops.enable\\_change\\_request\\_state\\_transition\\]\n\n
\n\nChange request callback timeout \\(in minutes\\)\n\n\n\nSet the timeout value in minutes until which the system will try to process a change when an inbound event goes into the waiting state during a pipeline run. After that the pipeline will be aborted. The reason for the error is displayed in your third-party tool's console logs. When a pipeline is cancelled because of callback timeout, the same information is added in the callback record of the corresponding step execution.\n\n\n\n120 minutes\n\n\n\n\\[sn\\_devops.change\\_request\\_callback\\_timeout\\]\n\n
\n\nDefault Bitbucket branch used for import request\n\n\n\nSpecify the default Bitbucket branch name that must be used to create an import request.\n\n\n\nmaster\n\n\n\n\\[sn\\_devops.bitbucket\\_default\\_branch\\]\n\n
\n\nClose code value for a change request completed successfully when the autoCloseChange parameter is enabled.\n\n\n\nEnter the close code value for a change request completed successfully when the autoCloseChange parameter is enabled.\n\n\n\nsuccessful\n\n\n\n\\[sn\\_devops.change\\_request.auto\\_close\\_successful\\_code\\]\n\n
\n\nClose code value for a change request completed with issues when the autoCloseChange parameter is enabled.\n\n\n\nEnter the close code value for a change request completed with issues when the autoCloseChange parameter is enabled.\n\n\n\nsuccessful\\_issues\n\n\n\n\\[sn\\_devops.change\\_request.auto\\_close\\_partial\\_successful\\_code\\]\n\n
\n\nClose code value for a change request completed unsuccessfully when the autoCloseChange parameter is enabled.\n\n\n\nEnter the close code value for a change request completed unsuccessfully when the autoCloseChange parameter is enabled.\n\n\n\nunsuccessful\n\n\n\n\\[sn\\_devops.change\\_request.auto\\_close\\_failure\\_code\\]\n\n
\n\nImport based evidence collection for orchestration capability\n\n\n\nThis property modifies how pipeline events are processed. When switched on, the setting reduces instance overhead by skipping step-level processing in the pipeline. The skipped step-level events will be ignored with the processing details, \"IGNORED: This event is ignored because the 'Import based evidence collection for orchestration capability' property is enabled\". Conversely, switching off reverts to the standard mode, where all inbound events undergo processing.\n\n\n\nFalse \\(disabled\\)\n\n\n\n\\[sn\\_devops.import\\_based\\_evidence\\_collection\\]\n\n
**Parent Topic:**[DevOps Change Velocity reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/devops-change-velocity/devops-change-velocity-reference.md)\n\n"}}