It happens to almost every dev, on almost every ticket. Here's why, and the one change that actually fixes it.
This is basically the reason I built Jitly in the first place, so I'm allowed to be a little opinionated here. Every developer I've ever worked with, myself very much included, forgets to move Jira tickets. Not once in a while — constantly. And it's not because anyone's lazy or doesn't care about the board.
Updating a Jira ticket requires you to stop what you're doing, switch context from your editor/terminal to a browser tab, find the ticket (which usually means searching because you closed that tab three hours ago), and manually change a dropdown. None of that is hard, but all of it happens at exactly the moment you're deep in flow state coding, or right after you finish something and you just want to move to the next thing.
Your brain treats "update the ticket" as a low-priority background task compared to "the code compiles" or "the tests pass." So it gets pushed to "I'll do it later," and later very often turns into two days later, or someone else asking you about it in standup.
Teams try Slack bots that ping you to update your tickets, or a rule that says "update Jira before you leave for the day." These help a little but they're fighting human nature — you're asking people to prioritize an admin task over the thing they actually get paid to do, which is write code. It doesn't stick.
Make the status update happen automatically as part of the action the developer is already taking. When you run jitly start ABC-123, the ticket moves to In Progress as a side effect of creating your branch — you didn't do an extra step, you just started working like normal. When you run jitly done, the status updates as a side effect of pushing your code. There's nothing to remember because there's no separate action to forget.