linode-cli-tickets

List your Support Tickets

$ linode-cli tickets list

$ linode-cli tickets create --summary "[Summary or quick title for the Ticket]" --description "[Detailed description of the issue]"

$ linode-cli tickets replies [ticket_id]

$ linode-cli tickets reply [ticket_id] --description "[The content of your reply]"

linode-cli tickets <command> [<args>] [<options>]
For specific command usage:
linode-cli tickets <command> --help

list
    Lists all active and pending support tickets associated with your Linode account. Provides a summary view of ticket IDs, subjects, statuses, and last updated times.

view <ticket_id>
    Retrieves and displays the full details of a specific support ticket, including all replies and associated service information. The <ticket_id> is a mandatory integer argument.

open --summary <summary> --description <description> [<service_id>]
    Opens a new support ticket. Requires a <summary> (ticket subject) and a detailed <description>. Optionally, you can relate the ticket to a specific Linode service (e.g., Linode, Domain, NodeBalancer, etc.) by providing its ID.

reply <ticket_id> --description <description>
    Adds a new reply to an existing support ticket. The <ticket_id> is mandatory, and the <description> contains the content of your reply.

close <ticket_id>
    Closes an open support ticket. This action marks the ticket as resolved. The <ticket_id> is a mandatory integer argument.

The linode-cli-tickets command is a subcommand of the linode-cli utility, providing a robust interface for interacting with Linode's support ticket system. It allows users to perform various actions related to support tickets, including listing existing tickets, viewing detailed information for a specific ticket, opening new support requests, replying to ongoing conversations, and closing resolved tickets. This command streamlines support interactions by enabling users to manage their Linode support needs directly from their terminal, integrating seamlessly into automated scripts or command-line workflows. It requires proper authentication with a Linode API token.

Using linode-cli-tickets requires a configured Linode API token with appropriate permissions (e.g., 'Read/Write' access for 'Support' or 'Global'). Without proper authentication or sufficient token scope, commands may fail or return unauthorized errors.

The linode-cli-tickets command inherits several global options from the parent linode-cli, which affect output formatting, pagination, and authentication:
--text: Displays results in a human-friendly table (default).
--json: Displays results in raw JSON format.
--format <columns>: Specifies a comma-separated list of columns to display in text mode.
--page <page_number> / --pages: Controls pagination for large result sets.
--token <token> / --env-token: Specifies the API token to use for the request.
--help: Displays help for the command or subcommand.

Interaction with the Linode API via linode-cli-tickets necessitates authentication. This is typically handled by configuring a Linode API token via linode-cli configure. The token grants the CLI permission to perform actions on your behalf. Ensure the token has the necessary 'Support' read/write scope.

As a component of the linode-cli, the tickets subcommand has evolved alongside the Linode API. Its functionality has consistently aimed to provide direct programmatic access to Linode's support system, adapting to new API versions and features. Its development reflects the broader commitment of Linode to offer comprehensive command-line tools for managing cloud resources.

linode-cli(1), linode-cli-account(1), linode-cli-linodes(1)