Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

jiractl

A small command-line tool for managing Jira issues and sprints, built on the standard library and go-atlassian.

It is instance-agnostic: your site URL, projects and workflow are read from a config file, and custom fields (story points, sprint) and workflow transitions are resolved from the Jira API at runtime — no instance-specific IDs are baked into the binary.

Features

  1. List issues in your open sprints
  2. List sprints
  3. Create an issue
  4. Change an issue's status (run, resolve, qa, done, close)
  5. Open an issue in the browser
  6. Describe an issue

Build

go build -o jira ./cmd

Setup

  1. Create a Jira API token: https://id.atlassian.com/manage-profile/security/api-tokens

  2. Register your credentials and site:

jira config -id <email> -pw <token> -d https://your-domain.atlassian.net -j <PROJECT>

This writes ~/.jira.

Usage

jira sprint            # list sprints
jira ls                # list your issues in the open sprints
jira open -m "message" -s <sprint id> -p <points>
jira describe -i <ISSUE-123>
jira view -i <ISSUE-123>
jira run -i <ISSUE-123>       # transition to "In Progress"
jira resolve -i <ISSUE-123>
jira qa -i <ISSUE-123>
jira done -i <ISSUE-123>
jira close -i <ISSUE-123>
jira help

Configuration (~/.jira)

username: you@example.com          # email
password: <api token>
domain: https://your-domain.atlassian.net
project: PROJ                      # default project for `open`
projects:                          # optional: projects included in `ls`/`sprint`
  - PROJ
  - QA
transitions:                       # optional: override workflow transition names
  run: In Progress
  resolve: Resolved
  qa: In QA
  done: Done
  close: Closed
storyPointField: ""                # optional: customfield_xxxxx, else auto-detected
sprintField: ""                    # optional: customfield_xxxxx, else auto-detected
  • transitions map each status command to a transition name. At runtime the tool fetches the transitions available on the issue and matches by name, so it works with any workflow. If a name is not found, the available options are printed.
  • storyPointField / sprintField are auto-detected from the field catalog by name when left empty. Set them explicitly if detection picks the wrong field.

About

Tool to manage Jira issues using command shell

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages