> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/customize-issue-fields-and-layouts/issue-fields/create-custom-issue-fields/issue-timer-fields/use-issue-timer-field-commands-manually-in-the-cli.md).

# Use issue timer field commands manually in the CLI

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.

<details>

<summary>Set timer fields</summary>

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:

```programlisting
!setIssue sla=30 slaField=timetoassignment
```

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

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

{% hint style="info" %}

### 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.
{% endhint %}

</details>

<details>

<summary>Start or stop timer fields</summary>

Run the following commands in the CLI:

| Command      | Description                                                                                                                                                                                                                                                                                                                                                                                            |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `startTimer` | <p>Starts the timer.</p><p>This command can also be used to restart a paused timer.</p><p>\*\*Example 14. \*\*null<br><br></p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>Timer fields are not started automatically when an issue is created unless run in a playbook.</p></div>                                                |
| `pauseTimer` | <p>Pauses the timer.</p><p>Use this command when a timer field has already started.</p><p>\*\*Example 15. \*\*null<br><br></p>                                                                                                                                                                                                                                                                         |
| `stopTimer`  | <p>Stops the timer.</p><p>\*\*Example 16. \*\*null<br><br></p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>After a timer field is stopped, before you can start the timer again you must reset the timer using the <strong>resetTimer</strong> command.</p><p>Timers are automatically stopped when an issue is closed.</p></div> |
| `resetTimer` | <p>Clears all fields for the timer.</p><p>This command must be used before restarting a timer that was stopped.</p><p>\*\*Example 17. \*\*null<br><br></p>                                                                                                                                                                                                                                             |

{% hint style="info" %}

### Note

When running commands in the CLI, you can specify the `alertID` to change the timer for a different issue.
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/customize-issue-fields-and-layouts/issue-fields/create-custom-issue-fields/issue-timer-fields/use-issue-timer-field-commands-manually-in-the-cli.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.