This documentation supports the 19.02 version of Remedy with Smart IT.

To view the latest version, select the version from the Product version menu.

Changing ticket status in Smart IT

The status shows what stage the ticket is at in its lifecycle. By updating this field when you: begin to work on a ticket, resolve the ticket, and so on, you ensure that the system keeps the applicable Service Level Agreements (SLAs) up-to-date (you can look at the SLA Progress Bar at the top of the ticket to see the current status of the SLA). For example, some SLAs can be configured to stop the clock if you change the Status to Pending, while with other SLAs, the clock continues to run until you change the status to Resolved or Closed.

In addition to keeping the SLAs up-to-date, updating the status is an important part of keeping the customer informed about what is happening with the request and for keeping your personal and group service statistics current. For example, if a ticket is cancelled, it's important to move the status to Cancelled so that the system does not continue to include it in your personal and group statistics and to ensure that the applicable SLA does not appear to be breached.

You cannot change the status of a ticket in certain situations. For example, you cannot change the status of an incident that is Closed. Only the status values for appropriate status transitions are displayed. For example, you cannot change the status of a work order from Rejected to In Progress. You cannot manually change the status of a service request ticket, except to cancel it.

To change the status

  1. From ticket details, open the status for editing:
      • (Universal client) Click the status value near the top of the ticket.
      • (Android devices) Tap the menu (three dots symbol), and then tap Edit.
      • (iOS devices) Tap Actions, and then tap Edit.
  2. Select the new status value from the list.
    For change requests, you can select a status from the list, or you can use buttons to set the next or previous status. For example, use the Set Next Status button (mobile clients) or Next button (universal client) to let the system select the next possible status value.
  3. If you are changing the status of an Incident request to Resolved, provide entries for the following categorization fields:
    • Status Reason.
    • Resolution Note. The Resolution Note is displayed as a tooltip in the ticket header after saving the ticket.


      The Operational Category and Product Category fields are also displayed on the panel. You can update all of the categorization fields when changing the status.

  4. Click or tap Save.

The following table lists the statuses that are available for incidents.

Incident status


AssignedChange to this status after the incident is assigned to a support group or individual for action, but before work begins on the incident.
CancelledChange to this status if work on the incident is cancelled.
ClosedChange to this status when the affected customer verifies the resolution (depending on how the system is configured, it can auto close incident tickets if the customer has not verified the resolution after a specified length of time).
In ProgressChange to this status when you begin work on the incident.
NewThis status is the default assignment value for all newly created incidents, before they are assigned to a support group or individual for action.
PendingChange to this status when you must wait for another action to take place before you can start or resume work on the incident (some SLAs can be configured to pause the clock while the incident is in the pending state).
ResolvedChange to this status when you have resolved the incident.

The Reopen button appears if an Incident is in Closed status. If an Incident is closed and you click Reopen button, a new Incident ticket is created and it relates the existing closed Incident.

Related topics

Process flow status and the lifecycle of an incident request Open link

(BMC Service Desk documentation)

  About work order status transitions Open link

(BMC Service Request Management documentation)

Service request life cycle Open link

(BMC Service Request Management documentation)

Managing your work in Smart IT consoles (update ticket status in bulk)

Incident rules Open link

(BMC Service Desk documentation)

Incident status reason definitions Open link

(BMC Service Desk documentation)

Change request status reasons Open link

 (BMC Change Management documentation)

Was this page helpful? Yes No Submitting... Thank you