When I was in FAANG, I despised ticketing. I was always the eng that refused to update. Then when I was a tech lead, I had the pain of pinging everyone for updates because they hated it too.
Things would go out of date, and then no one would really know if we were on track. We also had little visibility into what the team was doing outside of pinging/standups.
So I made an AI that looks at every commit you push and updates tickets for you. It can create tickets if there isn't one, update, leave comments, tag associated commits etc...
Basically, it's an "AI Board Babysitter" so you can just code and let it take care of the paperwork.
It's very much an MVP and I've got it integrated with a 10 person Startup.
Super quick 2 min set up, just integrates with Github + Linear and optionally Slack for action summaries.
I’d love feedback from fellow engineers, EMs, and PMs. Is this useful? What’s missing? What’s confusing? Would this slot into your workflow?
Give it a go: https://www.usevectra.com/
olism•5h ago
thomask1995•5h ago
Yea I am half way to a working Jira integration. Turns out, it works super differently than linear.
And yes! Talking to the AI in Slack is for sure a feature I want to support.
Just want to make sure I build the right thing. So sharing early