> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell/powershell-commands/get-rdmticket.md).

# Get-RDMTicket

Get-RDMTicket retrieves pending tickets from a configured ticketing service on the current Remote Desktop Manager data source.

### Synopsis

Retrieve tickets from a configured ticketing service.

### Syntax

#### Name

```
Get-RDMTicket [[-ServiceName] <string>] [-ForcePromptAnswer <DialogResult[]>] [<CommonParameters>]
```

#### ID

```
Get-RDMTicket -ServiceId <guid> [-ForcePromptAnswer <DialogResult[]>] [<CommonParameters>]
```

### Description

Retrieve the pending tickets from one of the current data source's log-enabled ticketing services. With no parameter the highest-priority service is used; -ServiceName or -ServiceId targets a specific one (list them with Get-RDMTicketingService). The same cmdlet works for every configured vendor.

### Examples

#### Example 1

```powershell
PS C:\> Get-RDMTicket
```

Retrieves tickets from the highest-priority ticketing service on the current data source.

#### Example 2

```powershell
PS C:\> Get-RDMTicket -ServiceName 'Support Jira'
```

Retrieves tickets from the ticketing service named 'Support Jira'.

### Parameters

#### -ForcePromptAnswer

Switch to use with caution. It will automatically answer prompt asking yes/no, yes/no/cancel, or ok/cancel questions. In case of multiple prompts, multiple values can be passed to this parameter. Here are the accepted values:

* Yes: Accept the prompt. Cover the OK and Automatic value.
* No: Refuse the yes/no/cancel prompt. "Cancel" is the fallback option if there is no "No" option.
* Cancel: Cancel the yes/no/cancel prompt. "No" is the fallback option if there is no "Cancel" option.

```yaml
Type: System.Windows.Forms.DialogResult[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -ServiceId

ID of the ticketing service to query, as listed by Get-RDMTicketingService.

```yaml
Type: System.Guid
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: ID
  Position: Named
  IsRequired: true
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -ServiceName

Name of the ticketing service to query. Defaults to the highest-priority service.

```yaml
Type: System.String
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: Name
  Position: 0
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Outputs

#### Devolutions.RemoteDesktopManager.Business.Shared.Ticketing.TicketingServiceTicket

### Notes

For more information, type "Get-Help Get-RDMTicket -detailed". For technical information, type "Get-Help Get-RDMTicket -full".


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell/powershell-commands/get-rdmticket.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.