Skip to main content

Bridge between Jira tickets and your local development workflow

Project description

⚡ Jitly

Bridge between Jira tickets and your local Git workflow.

Stop switching between Jira, terminal, and GitHub. Jitly connects them all — one command to start a ticket, one command to finish it.

jitly start ABC-123   # pulls base, creates branch, moves ticket → In Progress
jitly done            # commits, pushes, moves ticket → Done
jitly standup         # generates your daily standup in seconds

📺 Demo

Jitly Demo

▶️ Watch the full demo on YouTube


Why Jitly?

Every developer has done this manually:

  1. Open Jira → find ticket → copy ticket ID
  2. git checkout main && git pull
  3. git checkout -b feature/ABC-123-some-long-name
  4. Do the work...
  5. git add . && git commit -m "ABC-123: did the thing"
  6. git push --set-upstream origin feature/ABC-123-some-long-name
  7. Go back to Jira → move ticket to Done
  8. Get asked in standup — "what did you work on yesterday?"

Jitly automates all of this.

You define your team's policies once (branch naming, base branch, commit format) and Jitly enforces them automatically — for every developer on the team.

Standups become shorter. Scrum masters stop chasing ticket updates. Project managers get real-time visibility. Developers stay in flow.


Installation

pip install jitly

Works on macOS, Windows, and Linux with Python 3.9+.

Recommended on macOS:

pipx install jitly

Quick Start

Step 1 — Login to Jira

jitly auth login

Choose how you want to authenticate:

Method Best for
SSO / OAuth2 (browser) Jira Cloud with SSO
API Token Jira Cloud (email + token)
PAT / Password Jira Server or Data Center

Step 2 — Link your repo

Inside your git project:

jitly init

Connects the repo to a Jira project. Saves config to .jitly.yaml.

Step 3 — Set your workflow policy

jitly policy setup

Answer a few questions — set once, applies forever:

? Base branch to pull from:          main
? Branch name template:              feature/{ticket_lower}-{desc}
? Auto-pull base before branching?   Yes
? Commit message template:           {ticket}: {desc}

Step 4 — Start a ticket

jitly start ABC-123

Jitly will:

  • ✅ Fetch ticket details from Jira
  • ✅ Handle uncommitted changes (stash / push / discard / cancel)
  • ✅ Pull latest from base branch
  • ✅ Create feature/abc-123-your-ticket-title
  • ✅ Move ticket to In Progress on Jira automatically

Step 5 — Finish the ticket

jitly done

Jitly will:

  • ✅ Commit all changes (auto-fills message from ticket)
  • ✅ Push to remote
  • ✅ Show available Jira statuses fetched live — move ticket to Done / In Review / Ready for QA

Step 6 — Daily Standup

jitly standup

Jitly will:

  • ✅ Pull yesterday's commits from git automatically
  • ✅ Show today's active ticket
  • ✅ Ask for any blockers (stored and tracked)
  • ✅ Generate a copy-paste ready standup format for Slack / Teams / email

Example output:

⚡ Jitly Standup

╭──────────────┬──────────────────────────────────────────╮
│ Yesterday    │ • ABC-123: Add login page                │
│              │ • ABC-124: Fix null pointer on dashboard │
│ Today        │ • Working on ABC-125: Add dark mode      │
│ Blockers     │ • None                                   │
╰──────────────┴──────────────────────────────────────────╯

── Copy-paste format ──
*Yesterday:*
  • ABC-123: Add login page
  • ABC-124: Fix null pointer on dashboard
*Today:*
  • Working on ABC-125: Add dark mode
*Blockers:*
  • None

All Commands

jitly auth login        Login to Jira (SSO, API token, or PAT)
jitly auth logout       Remove saved credentials
jitly auth whoami       Show currently logged in user

jitly init              Link this repo to a Jira project

jitly policy setup      Interactive policy wizard
jitly policy show       View current policy
jitly policy set        Set a single policy value

jitly start <TICKET>    Start working on a Jira ticket
jitly done              Commit, push, and wrap up current ticket
jitly standup           Generate your daily standup update
jitly status            Show active ticket, branch, and git state

Branch Name Templates

Customize how branches are named using tokens:

Token Output
{ticket} ABC-123
{ticket_lower} abc-123
{desc} add-login-page (slugified summary)

Examples:

feature/{ticket_lower}-{desc}   →   feature/abc-123-add-login-page
{ticket}/{desc}                 →   ABC-123/add-login-page
bugfix/{ticket_lower}           →   bugfix/abc-123

Commit Message Templates

Token Value
{ticket} Jira ticket ID
{desc} Ticket summary
{message} What you type at prompt

Examples:

{ticket}: {desc}            →   ABC-123: Add login page
[{ticket}] {message}        →   [ABC-123] fixed null pointer issue
feat({ticket}): {desc}      →   feat(ABC-123): Add login page

Smart Branch Detection

If someone already started working on ABC-123 and pushed a branch — Jitly detects it automatically:

Branch feature/abc-123-add-login already exists on remote.
Someone may have already started this ticket. Fetching their work...
✓ Checked out existing branch feature/abc-123-add-login

No manual git fetch or git checkout needed.


Uncommitted Changes Handling

Run jitly start while you have unsaved work? Jitly asks:

? You have uncommitted changes on feature/old-branch. What would you like to do?
  > stash    — save changes, switch ticket, restore later
    push     — commit & push current changes first
    checkout — discard all changes and switch (irreversible)
    cancel   — abort

Multi-Project Support

Jitly works across multiple projects and machines:

  • Each repo has its own .jitly.yaml with project-specific policy
  • Same project on a new machine? Run jitly init — policy syncs automatically from backend
  • Policy hierarchy: Project policy → Global policy → Default

Supported Jira Versions

Version Auth Method
Jira Cloud SSO / OAuth2, API Token
Jira Server PAT, Username + Password
Jira Data Center PAT, Username + Password

Configuration

Jitly stores your global config at ~/.config/jitly/config.yaml.

Per-project config is saved in .jitly.yaml (add to .gitignore).

Environment variables:

Variable Default Description
JITLY_BACKEND_URL auto Jitly backend URL

Requirements

  • Python 3.9+
  • Git

Links


License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

jitly-0.1.7.tar.gz (20.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

jitly-0.1.7-py3-none-any.whl (23.4 kB view details)

Uploaded Python 3

File details

Details for the file jitly-0.1.7.tar.gz.

File metadata

  • Download URL: jitly-0.1.7.tar.gz
  • Upload date:
  • Size: 20.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.13

File hashes

Hashes for jitly-0.1.7.tar.gz
Algorithm Hash digest
SHA256 f49609775e19603b69ff6f9c5eb9a7bb7f04ca7581cfc304eb3197c5669e179d
MD5 c0becce244be99c685f96f23e670f57a
BLAKE2b-256 9901060536b6bb7bd9d0838fbcc8be290181cad4bcc2bacbf4ff3ff4c5cb6128

See more details on using hashes here.

File details

Details for the file jitly-0.1.7-py3-none-any.whl.

File metadata

  • Download URL: jitly-0.1.7-py3-none-any.whl
  • Upload date:
  • Size: 23.4 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.13

File hashes

Hashes for jitly-0.1.7-py3-none-any.whl
Algorithm Hash digest
SHA256 50917d1264008e24c5edd5bf504ebec6330603e07ecdcaa0ab8eeddc8e792033
MD5 a00ca754f05106d50d63db770aabc649
BLAKE2b-256 1ef6b8f8b10fb5ba656149635c6eb9a84ed10bcc4131d283bcf93b4c34e8e296

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page