#productivity #tui #jira #terminal

app do-next

Pick your next Jira task & manage it from the terminal

2 releases

Uses new Rust 2024

new 0.0.0-2026.4.8 Apr 8, 2026
0.0.0-2026.3.19 Mar 19, 2026

#267 in Development tools

MIT/Apache

435KB
11K SLoC

do-next

[!IMPORTANT] Experimental & unstable! I'm exploring the problem space. Everything might change.

Pick your next Jira task & manage it from the terminal.

Pre-release state

Right now do-next is intended for internal use in my teams.

v0.0.0-yyyy.mm.dd is the versioning scheme before the release.

Polished experience and documentation are coming closer to the first public release.


Installation

The main way before the release is to build from source.

Following solutions are supported at the best effort:

Binaries

Download a compiled binary from GitHub Releases

Rust way

Pre-release versions have to be provided explicitly:

cargo install do-next@0.0.0-yyyy.mm.dd

The latest published version: Crates.io Version

Nix way

This repo provides a flake. I guess, you know how to configure in on your own ^.~

nix run github:ejiektpobehuk/do-next

Runtime dependencies

macOS and Windows have no extra dependencies.

Linux depends on:

  • xdg-utils to open Issues in a browser
  • dbus & secret service provider for optional keyring secret management

Quick start

do-next has a built-in onboarding.

do-next auth to reconfigure authentication only.


Development

Dependencies:

  • justoptional command runner
  • cargo — the Rust package manager
  • msrv — 1.88.0
  • dbus — Linux specific dependency

just acts as a cargo wrapper that overwrites some defaults and provides a wrapper for NixOS dev shell.

Run just to list all available commands:

just
Available recipes:
    build
    check
    default
    lint
    lint-fix
    run
    shell
    test

NixOS

libdbus is a runtime and a build dependency. You'll need the dev shell to handle it properly. just handles calling the dev shell if it detects that it's running in a NixOS environment.

Non-NixOS Linux

The sync-secret-service keyring backend requires the dbus development headers:

Arch Linux

sudo pacman -S dbus pkgconf

Debian/Ubuntu

sudo apt install libdbus-1-dev pkg-config

Fedora

sudo dnf install dbus-devel pkgconf-pkg-config

macOS / Windows

just build

or

cargo build

No extra system dependencies required.


License

Licensed under either of MIT or Apache-2.0 at your option.

Dependencies

~44–85MB
~1M SLoC