Hey folks 👋 — short post.
I've been working on imdone-cli and imdone desktop, workflow tools that let you manage Jira issues as markdown files directly in your project repo.
A lot of developers have checked out the pricing page lately, but no one was converting at the $18/month price point. Some have tried the free plan but hit the wall when they need attachments and comments — that's where the real context lives.
So I'm running a very short pricing experiment starting December 1st for one week:
$9/month for single developers (normally $18)
Same features. Same workflow. Full access to attachments, comments, and everything else.
What problem does this solve?
Ever lose 20 minutes hunting for that Jira comment that explained why something was built a certain way?
Or spend half your sprint context-switching between your IDE, browser tabs, and Jira just to understand what you're supposed to be working on?
That fragmented context kills momentum.
imdone-cli and imdone desktop help you:
- Build with clear, de-fragmented context — everything in one place
- Work with Jira issues as markdown files in your repo
- Keep story context, attachments, and comments right where you code
- Stop bouncing between browser tabs and your IDE
- "Work Jira like Git" — push, pull, diff and merge
Why am I doing this?
Honestly, I want to understand if pricing is the barrier or if there's something else I need to fix. This experiment will help me figure that out.
If you work with Jira every day and want to keep context closer to your code, this might be useful.
No pressure. Just sharing the experiment.
If you've tried imdone-cli or imdone desktop, I'd love to hear what worked — and what didn't. Drop a comment or reach out directly.
Top comments (0)