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
- Avoid duplicate work
- Maintain accountability
But a new problem started.
The Real Pain: Tab Chaos
Every time I needed to commit a ticket:
- Open Jira
- Find the ticket
- Copy the ID
- Switch back to GitHub
- Write the commit
- Re-check acceptance criteria
- Switch again
- Open another tab
- Lose context
Sometimes I reused the same tab.
Sometimes I opened new ones.
Either way — I kept breaking flow.
When you’re working across multiple tickets?
It’s chaos.
It Got Worse…
While committing, I often needed to check:
- Edge cases mentioned in comments
- Special instructions
- Whether something should not go to production yet
- Small requirements hidden in discussion threads
I even started writing personal reminders in Notepad.
And sometimes?
I forgot to review them before pushing.
That’s risky.
The Real Problem Was Context Switching
The issue wasn’t copying ticket IDs.
It was losing context.
Jira lived in one tab.
GitHub lived in another.
My notes lived somewhere else.
My brain became the integration layer.
And that’s not scalable.
Demo
My Experience with GitHub Copilot CLI
So I Built a Chrome Extension
Instead of accepting the chaos, I built a Chrome extension that connects Jira context directly inside GitHub.
View Jira Tickets Inside GitHub
- Hover over a ticket ID
- Instantly see ticket details in a tooltip
- Open Jira in a side panel without leaving GitHub
No more full tab switching.
No more breaking flow just to re-read acceptance criteria.
Personal Notes Per Ticket
I added a feature to:
- Save private notes per ticket
- Review them before merging or pushing
No more scattered Notepad files.
Everything stays attached to the ticket.
Lightweight Configuration
Simple setup for Jira instance
Quick toggle for tooltip behavior
Minimal friction
It works quietly in the background.
How I Built the UI (With GitHub Copilot in terminal)
For the UI layer, I experimented with AI-assisted development using GitHub Copilot terminal. Since this is a Chrome extension, the UI had to be built using plain JavaScript along with HTML and CSS, with no heavy frameworks and no React setup, just lightweight scripts injected directly into GitHub’s DOM. Instead of manually scaffolding every component, I described the UI structure in comments and let Copilot suggest layout patterns, tooltip logic, and side panel structures. I iterated on those suggestions, refined the styling and interactions step by step, and adjusted state handling to fit the extension environment. Copilot accelerated the repetitive parts such as structuring the popup, creating consistent UI elements, and wiring basic state flows, while I focused on the core logic, workflow decisions, and overall UX design. It did not replace thinking; it acted like a fast UI assistant. The result was a clean, lightweight interface that solves a real problem without overengineering it.
What’s Next?
I’m still improving it.
If you’ve faced similar Jira + GitHub workflow problems, I’d love to hear how you solved them.
Because at the end of the day:
Great engineering isn’t just about code.
It’s about designing better systems — including how we work.