DEV Community

Cover image for I Got Tired of Jira Breaking My Flow State, So I Built a Local App to Bypass It (SheepCat v1.3)
Andrew Chadwick
Andrew Chadwick

Posted on

I Got Tired of Jira Breaking My Flow State, So I Built a Local App to Bypass It (SheepCat v1.3)

We have all been there. You are deep in the zone, holding a complex mental model of a C# backend or untangling a massive SQL query. Then, the inevitable message drops: "Hey, can we get a quick status update on ticket LM-62401?"

​To answer, you have to switch to your browser, wait for the heavy Jira or Azure DevOps UI to load, navigate the endless boards, find the ticket, and type out what you did. By the time you get back to your IDE, your working memory has completely crashed. The context is gone.

​That cognitive tax the constant friction of administrative context-switching is brutal.
​So, I decided to engineer a workaround.

​## Enter SheepCat 🐑🐈‍⬛

​SheepCat is an open-source, locally run desktop app I built to track my daily work without leaving my flow state. The premise is simple: log what you do, as you do it, in a lightweight, frictionless local interface.

​But with the release of v01.03.00, it just got a massive upgrade that completely eliminates the "PM Interruption."
​The New Release: Direct API Pushes to Jira & Azure DevOps
​Up until now, SheepCat was great for keeping a local ledger of my day. But I still had to manually copy-paste that data into the corporate trackers eventually.

​With v1.3, I’ve implemented an External API Service Factory. Now, SheepCat talks directly to your project management tools.

​## Here is how the new workflow looks:

​Stay Local: Log your micro-updates, debugging steps, and code changes directly into SheepCat throughout the day.

Batch Select: At the end of the day (or when you are at a natural stopping point), open the new scrollable "Send Updates" dialog.

Push to Production: Multi-select the entries you want to share, and SheepCat fires them directly to Jira or Azure DevOps via API.

​No opening browsers. No hunting for tickets in heavy UIs. You just push the update from your desktop and get right back to the code.

​## The Philosophy: Systemic Adaptation

​I originally started building tools like SheepCat because, as a neurodivergent developer, the standard corporate workflow (high context-switching, rigid administrative tracking) drains my mental battery incredibly fast.

​But what I've found is that reducing cognitive load benefits everyone. Whether you have ADHD, dyslexia, or you are a neurotypical senior dev who just wants to stay focused on the architecture, engineering your environment to remove friction is a superpower.

​(If you are interested in this kind of workflow hacking, we recently started a community to share these exact types of "janky" survival tools over at r/LobACob!)

​Give it a Try (and Break My Code)
​SheepCat is fully open-source. If you are tired of the Jira UI tax, grab the latest v01.03.00 release and try the direct integration.
​Get the v1.3 Release on GitHub
​If you end up using it, drop a star on the repo! And if you want to add integrations for other tools (Linear, Trello, Asana), PRs are incredibly welcome.

Top comments (0)