Hey there 👋,

Quick question: How many times today did you switch from your editor to your browser just to update an attachment in Jira?

If you're like most developers I talk to, it's probably too many.

Update a screenshot? Browser.

Fix a diagram? Browser.

Upload a new error log? Browser.

Each time, you lose 5-10 minutes. Not just to the task itself, but to finding the right tab, scrolling to attachments, uploading, deleting the old version, and trying to remember what you were coding.

It's exhausting.

━━━━━━━━━━━━━━━━━━━━━━

Here's what changed in Imdone CLI 0.39.0:

Attachments are now just... files.

They live in your repo, alongside your code. Edit them with your local tools. Push changes like you push code.

No browser. No context switching. No flow interruption.

━━━━━━━━━━━━━━━━━━━━━━

Here's what you can do now:

→ MODIFY an attachment

 Edit screenshot.png locally

 Run: imdone push

 ✓ Updated in Jira, old version deleted automatically

→ DELETE an attachment

 rm old-diagram.png

 Run: imdone push

 ✓ Removed from Jira

→ RENAME an attachment

 mv draft.pdf final.pdf

 Run: imdone push

 ✓ Old file deleted, new file uploaded

→ ADD a new attachment

 cp error-log.txt backlog/current-sprint/PROJ-123/attachments/

 Run: imdone push

 ✓ Uploaded to Jira

One command. Zero browser tabs.

━━━━━━━━━━━━━━━━━━━━━━

Why this matters:

When you're fixing a bug, everything you need should be in one place:

- The code (your editor)

- The issue description (markdown file)

- The screenshots (local files)

- The error logs (local files)

Not scattered across your editor and 15 browser tabs.

That's what we built.

━━━━━━━━━━━━━━━━━━━━━━

The technical stuff (for the curious):

We use git to detect changes before the pull operation runs. This prevents the stash/pop cycle from interfering with deleted/renamed file detection.

We upload new versions BEFORE deleting old ones. If the upload fails, your old version stays in Jira. No data loss.

All attachment metadata is tracked locally. The system knows which files are new, modified, or deleted.

━━━━━━━━━━━━━━━━━━━━━━

Want to try it?

npm install -g imdone-cli

imdone init

(follow the prompts)

imdone pull

(edit any attachment)

imdone push

That's it.

Your attachments sync to Jira. Your flow stays intact. Your browser stays closed.

━━━━━━━━━━━━━━━━━━━━━━

Reply and let me know what you think. Or if there's another Jira pain point you want solved.

I'm listening.

- Jesse

P.S. - This works with comments too. Add them in your editor, push to Jira. Two-way sync for everything: issues, comments, attachments. All as markdown and files. All in your repo.

---

Imdone CLI - Two-way sync for Jira

https://npmjs.com/package/imdone-cli