Ticketron (tix)
@karolswdev
About Ticketron (tix)
Ticketron (tix) is a CLI tool designed to quickly create JIRA issues based on brief user input, leveraging LLMs for detail generation and an MCP server for JIRA interaction.
Basic information
Config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Ticketron (tix)?
Ticketron (tix) is a command‑line tool that uses Large Language Models (LLMs) via OpenAI to simplify creating and searching JIRA tickets. It integrates with the jira‑mcp‑server for JIRA communication and is designed for developers and ops teams who want faster ticket management.
How to use Ticketron (tix)?
Install with go install github.com/karolswdev/ticketron/cmd/tix@latest, then run tix config init to create the configuration directory. Set your OpenAI API key with tix config set-key <key> (or via the TICKETRON_LLM_API_KEY environment variable). Use tix create to create tickets using natural language and tix search to search tickets with JQL or plain English.
Key features of Ticketron (tix)
- Create JIRA issues using natural language
- Search JIRA issues using JQL
- Contextual ticket generation via LLM
- Secure API key storage (OS Keychain or env var)
- Shell completion for Bash, Zsh, Fish, PowerShell
- Structured output formats (JSON, YAML, TSV)
Use cases of Ticketron (tix)
- Quickly create a bug report by describing the issue in plain English
- Search for your open tickets across projects using conversational phrases
- Enrich ticket creation with persistent project context from a
context.mdfile - Generate structured (JSON/YAML/TSV) reports of ticket searches for further analysis
FAQ from Ticketron (tix)
What are the dependencies and runtime requirements?
Ticketron requires Go 1.23.8+, a running instance of the jira‑mcp‑server, and an OpenAI API key. Make is needed for development tasks.
How does Ticketron store the OpenAI API key?
The API key can be stored securely in the OS keychain using tix config set-key or set as the environment variable TICKETRON_LLM_API_KEY. It is never stored in plain‑text configuration files.
Where does Ticketron store its configuration and data?
Configuration files (config.yaml, links.yaml, system_prompt.txt, context.md) live in ~/.ticketron/. The API key is stored separately in the OS keychain or an environment variable.
What transport does Ticketron use to communicate with JIRA?
Ticketron relies on the jira‑mcp‑server, which uses the Model Context Protocol (MCP) for communication. The MCP server URL must be specified in config.yaml.
Are there any known limits?
Ticketron requires an active internet connection to reach the jira‑mcp‑server and the OpenAI API. It does not work offline or without these external services.
Comments