Hey — quick New Year’s “resolution” for your Jira workflow 😄
Ever notice how Done in Jira doesn’t always mean resolved?
Jira separates two concepts:
- Status: where the work is in the workflow
- Resolution: why the work ended (Fixed, Won’t Fix, Duplicate, etc.)
Here’s the nuance: depending on how your Jira workflow is configured, Jira might prompt you for a Resolution, auto-set it, or not ask at all — which is how issues end up “Done” but still “Unresolved” in dashboards and JQL.
That’s the paper cut I wanted to eliminate.
imdone-cli 0.28.0: move to Done without the extra decision
In 0.28.0, when you move an issue into a Done status category, imdone-cli will automatically set Resolution to Done if it’s empty — so you can close work without getting pulled into one more dropdown.
>_imdone move PROJ-123 Done
A couple details that matter:
- Never overwrites an existing resolution
- Non-blocking: the move succeeds even if setting resolution fails
- Only applies when moving into a “Done” status category
Command options (if you do want control)
Set a specific resolution when moving to Done:
>_imdone move PROJ-123 Done --resolution "Fixed"
Skip setting resolution even when moving to Done:
>_imdone move PROJ-123 Done --no-resolution
Interactively choose a resolution (with a Skip option):
>_imdone move PROJ-123 Done --prompt-resolution
The interactive option fetches the available resolutions from Jira (including descriptions). If the API call fails, it falls back to a common list so you’re not blocked.
If you’ve ever been bitten by “Done but Unresolved,” this should make your 2026 a tiny bit smoother.
Happy New Year,
Jesse
P.S. Move command docs (including all resolution behavior + flags): https://www.npmjs.com/package/imdone-cli#user-content-move--move-issue-to-new-status
0 comments