4 ms·

How has the process of adopting tickets been for you? Do they often require significant rewrite/additional context? As at least everywhere I have worked, the ba

How has the process of adopting tickets been for you? Do they often require significant rewrite/additional context? As at least everywhere I have worked, the backlog is full of single sentence context free bugs that are obvious to the product owner and anyone who has worked there for a while, but are useless to anyone new. For example, in my first job, I was tasked with greying out a button after it had been clicked. Trivial and generic task. But I was paired with a brand new senior to do the work and we spent a day trying to find the correct button (being new and wanting to seem useful, we didn't want to ask).

hzia 3y ago
It's the main topic for majority of my calls with engineering teams using GitStart (Other than convincing them at times to add auto formatting, linting and basic guardrails to your codebase lol) It got a lot better with covid which started the wave of remote work and teams started to care about writing tickets for the first time. Currently we solve it with ticket templates, but we are now doubling down on using AI to help craft and improve ticketing writing. It’s still under private beta, but will be live for everyone soon https://gitstart.com/changelog/tickets-by-chat https://gitstart.com/changelog/tickets-by-chat
- hmcq6 3y ago
  > teams started to care about writing tickets for the first time. Do you mean your team? Because this would be an absolutely ludicrous thing to state generally. > using AI to help craft and improve ticketing writing. Right so speaking of AI, how do you plan to keep up with github copilot and how can customers be sure that you're not just using copilot under the hood?