For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex Cloud Runtime

Update issue fields

Update issue fields to maintain accurate investigation context.

Use setIssue to update supported issue fields. Use setIssueStatus to update an issue’s status or resolution.

Run these commands in the War Room CLI, a script, or a playbook task.

You can update issue fields by running the setIssue and setIssueStatus commands in the CLI, in a script, or a playbook task.

  • setIssue: Sets values for specific issue fields. The supported fields are presented in the list of arguments.

    The following examples show how to run the setIssue command in the CLI. You can run CLI commands in the War Room. When you start typing the CLI provides the available options and if you select an enum field, the CLI provides the available values.

    • To change the issue severity to high, run:

      !setIssue severity=high
    • To change the issue severity to high and star the issue, run:

      !setIssue severity=high starred=true
  • setIssueStatus: Sets the status or resolution value for an issue. This command supports the status argument, which presents a list of status and resolution type values. The selected status is set in the custom_status field.

    If you specify a resolution status, the issue is closed and the resolution_status and closeReason fields are updated to the same value as the custom_status field. If you specify a New, Reopened, or Under Investigation status, the issue remains open and the resolution_status and closeReason fields are empty.

    You can create custom issue statuses and resolution reasons, and use the setIssueStatus command to set these custom statuses for issues.

    Tip: You can create custom issue statuses and resolution reasons. Use setIssueStatus to set these statuses for issues.

    For example, an investigation changes an issue from New to Under Investigation. You can create an interim status, such as Triage. Review Resolution reasons for cases and issues before creating a custom status.

    Example The following examples show how to run the setIssueStatus command in the CLI. You can run CLI commands in the War Room. When you start typing, the CLI provides the available options and if you select an enum field, the CLI provides the available values.

    • To change the issue status to Resolved - Known Issue, run:

      !setIssueStatus status="Resolved - Known Issue"
    • To change the issue status to custom status Triage, run:

      !setIssueStatus status=Triage

    Note

    You must create a custom status before you can select it.

Example

The following example shows how the setIssueStatus command can be used in a playbook task. In this example, the task sets a custom issue status (Triage). The custom issue status was created before setting up the playbook.

setAlertStatus_playbook_example.png

Last updated

Was this helpful?