Use issue timer field commands manually in the CLI

Manage Cortex AgentiX issue timer fields manually with CLI commands.

You can manage the timers for a specific issue by running commands manually in the CLI. By running CLI command you can to manage timers on a more granular level within specific issues when the need arises. For example, for a high severity issue you might need to decrease the response time.

Set timer fields

Use the setIssue command to set a specific issue due date, or to set a specific timer field in an issue. If you add the sla parameter to the command, it sets the time for the issue's due date. If you also add the slaField you set the timer for the issue field.

Example 13.

To change the Time to Assignment field target to 30 minutes in the current issue, run the following command:

!setIssue sla=30 slaField=timetoassignment

To change the timer to February 1, 2024, at 11.12 am, run the following command:

!setIssue sla=2024-02-01T11:12

Note

When defining the values for the slaField use the machine name for the field, which is lowercase and without spaces. You can check the machine name by editing the issue field.

Start or stop timer fields

Run the following commands in the CLI:

Command	Description
startTimer	Starts the timer. This command can also be used to restart a paused timer. **Example 14. **null Note Timer fields are not started automatically when an issue is created unless run in a playbook.
pauseTimer	Pauses the timer. Use this command when a timer field has already started. **Example 15. **null
stopTimer	Stops the timer. **Example 16. **null Note After a timer field is stopped, before you can start the timer again you must reset the timer using the resetTimer command. Timers are automatically stopped when an issue is closed.
resetTimer	Clears all fields for the timer. This command must be used before restarting a timer that was stopped. **Example 17. **null

Note

When running commands in the CLI, you can specify the alertID to change the timer for a different issue.