A simple command-line client for Atlassian Jira written in Go, featuring context-aware configuration and custom commands.
go-jira is a command-line client for Atlassian Jira that allows users to interact with Jira issues directly from the terminal. It solves the problem of slow, browser-based Jira navigation by providing a fast, scriptable interface for creating, viewing, editing, and managing issues. The tool supports context-aware configuration, custom commands, and flexible authentication methods.
Developers, DevOps engineers, and teams who frequently use Jira for issue tracking and want to streamline their workflow through terminal commands and automation scripts.
Developers choose go-jira for its simplicity, powerful customization via templates and custom commands, and seamless integration into shell environments. Its context-aware configuration reduces repetitive typing, and support for secure credential storage makes it suitable for automated pipelines.
simple jira command line client in Go
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically loads project-specific settings from .jira.d directories in the current path hierarchy, reducing manual setup for multi-project workflows as detailed in the configuration section.
Supports defining custom commands with arguments, options, and templating, enabling automation of complex Jira operations through YAML configuration and shell scripts.
Integrates with keyring, pass, and gopass for secure credential storage, and supports API tokens and session-based auth for various Jira setups, including Atlassian Cloud.
Provides a debug template to output JSON data for any operation, helping users understand and customize templates using Go's text/template engine.
The recursive configuration hierarchy and dynamic executable config files require familiarity with YAML, shell scripting, and environment variables, which can be overwhelming for new users.
Setting up secure password sources like keyring or pass involves additional external tools and setup steps, adding friction compared to simpler credential storage methods.
Due to GDPR changes, the tool has transitioned from username to email-based authentication, causing potential confusion in configurations and requiring updates, as noted in the disclaimer.