Microsoft's project + pipeline platform
Azure DevOps Boards is Microsoft's integrated boards, repos, and pipelines suite, common in .NET and enterprise shops.
Azure Boards has genuinely tight integration with Azure Repos — commit messages with work item IDs (`AB#123`) auto-link and can auto-transition items, similar in spirit to what Jitly does for Jira.
This tight integration only exists if you're also using Azure Repos. The moment your team uses GitHub or GitLab instead (which a lot of teams do even inside Microsoft shops), that automatic linking disappears and you're back to manual updates.
This is really the whole reason Jitly exists — it's not trying to replace Azure DevOps Boards at what Azure DevOps Boards is good at. Jitly's job is narrower and more specific: jitly start ABC-123 creates your branch and moves the Jira ticket to In Progress in one shot, jitly done commits, pushes, and updates the status to whatever your team's workflow has, fetched live so it never gets out of sync with how your Jira is actually configured.
And it's not just a CLI anymore — the Jitly VS Code extension does the same job visually: a sidebar with your Jira tickets, one-click start, pause work with a WIP push, done with live status transitions, and a one-click standup generator. Same project config and policies as the CLI, so a team can mix both.
Mainly teams fully inside the Microsoft/Azure ecosystem using Azure Repos as their git host. If that's not you, this comparison probably isn't that relevant to your day — Azure DevOps Boards and Jitly solve different problems most of the time.
pip install jitly) or a VS Code extension. They're rarely a straight either/or choice — most teams comparing them are really deciding what to combine with what they already use.