Jira Ticket Finder

Make releases easier by determining which Jira tickets have been completed since the last release.

This script will:

Search through git repositories in the current working directory (or specific repos you provide)
Find the latest git tag in each repository
Extract Jira ticket numbers from commit messages since that tag
Output a summary of all found ticket numbers

Installation

# This package depends on bun being installed globally
# See: https://bun.sh/docs/installation
npm i -g bun

# Creates a global `jira` cli command
npm i -g jira-ticket-finder

Usage

cd /parent/dir/of/group/of/repos

jira [options]

Options:

Option	Default	Description	Example
`-r`, `--repo`	All git repos in current directory	Specific repositories to search. Can be repo names or paths or globs.	`repo1`, `../repo1`, `~/foo/repo1`, `"foo/*"`
`-x`, `--exclude-repo`	-	Specific repositories to exclude. Can be repo names or paths or globs.	`repo1`, `../repo1`, `~/foo/repo1`, `"foo/*"`
`-p`, `--prefix`	Any Jira prefix	Jira project prefixes to look for	PROJ, TEST
`-t`, `--tag-pattern`	Latest tag in each repo	Glob pattern to match version tags	`"v"`, `".."`
`-m`, `--max-tickets`	30	Maximum number of tickets before repo is considered invalid	100
`-c`, `--to-commit`	main/master	Commitish to stop searching at	ad233f8, HEAD, my-branch
`-n`, `--no-fetch-latest`	false	Skip fetching latest repo data before searching	-
`-h`, `--help`	-	Display usage guide	-

Examples:

Search all repositories in the current directory:

jira

Search specific repositories:

Names of repos in the current directory, or paths to repos, can be provided. Glob patterns can be used to match multiple repositories.

jira --repo repo1 repo2
jira --repo ~/dev/repo1 --repo ../repo2
jira -r "files*"

Search for specific Jira ticket prefixes:

jira --prefix PROJ TEST
jira --prefix PROJ --prefix TEST

Search for a specific tag pattern:

Specify a glob pattern to use for matching version tags. Default is to use the latest tag.

jira --tag-pattern "v*"
jira --tag-pattern "*.*.*"
jira -t "v[0-9]*"

Set a different threshold for maximum tickets per repository:

The assumption here is that if a single repo has more than a certain number of tickets found, that something has gone wrong and those tickets are invalid for some unknown reason. If that is not the case, you can use this setting to increase the threshold.

jira --max-tickets 50