From Tab Chaos to Clarity: Why I Built a Chrome Extension for Jira + GitHub

This is a submission for the GitHub Copilot CLI Challenge What I Built A Chrome extension but let me tell you about the problem first. If you work in a team where: Jira tickets aren’t pre-assigned Multiple developers resolve tickets dynamically Ticket status determines what goes to production Commits are used to track ownership Then you probably know this problem. It’s not about writing code. It’s about tracking responsibility — without losing your mind. The Workflow We Had In our setup: Developers pick up tickets freely. Whoever solves it moves the status. A tracker reports resolved tickets to the project manager. Production pushes depend on knowing which tickets were completed and by whom. Since assignees aren’t fixed beforehand, the most reliable source of truth became: Git commits. So we started adding Jira ticket IDs inside commit messages. Example: feat: add validation for payment form (PROJ-142) This helped us: Identify who solved which ticket Track what goes to dev vs prod Avoi