Hi HN,
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/
Cool concept, but my team uses Jira and it’s not easy to move off. Any plans to integrate Jira? Also let’s say the AI makes a change I don’t like, is there an undo/correct functionality in Slack?
I use it and I love checking it in the morning to see what my team is up to, I don’t have to ping people and break their flow.
It helps us figure out what got done and where we are in our roadmap
How does it decide what ticket to associate a commit with, or when to create a new one ?
I am a bit reluctant to try it out because this will give access to my company source code, and that is a no go for a no-name, no-certification tool without even a privacy page. Have you considered that trust will give the highest entry barrier to your tool?