CI pipelines can auto-tag or auto-merge branches, but they can't help you before you even push.
Some teams set up CI jobs that do things like auto-label PRs based on branch name patterns, or auto-transition Jira tickets when a PR merges using something like the Jira/GitHub Actions integration. That's a valid approach and it does solve the "ticket didn't move" problem after the fact.
The gap is it only kicks in after you've already pushed and opened a PR. It doesn't help with the actual branch creation, the naming, or getting the ticket to In Progress the moment you start. Jitly covers the whole loop, start to finish, from your terminal, before anything even hits GitHub.
You can honestly run both. Jitly handles the local start/done loop, and a CI action can still do the final "PR merged → close ticket" step as a safety net in case someone bypasses Jitly.