What would make sense for me is to use an AI to turn implicit context that is only there in the moment into explicit context that is stored in the ticket.

E.g. maybe you have your application open in a browser and are currently viewing a page with a very prominent red button. You hit that /issue command with "button should be yellow not red".

That half-sentence makes sense if you also have that open browser window as context, but would be completely cryptic without.

An AI could use both the input and the browser window to generate a description like "The background color of the #submit_unsafe button widget in frontend/settings/advanced.tsx should be changed from red to yellow." or something.

Sort of like a semantic equivalent to realpath if you want.

I do see utility in that.

▲

nix0n 3 hours ago | parent | next [-]

I think a URL and screenshot would be way more useful than a bunch of text for that use case.

	▲	swores an hour ago \| parent [-]
		But maybe the button only appears on that URL if you've first pressed something else, or if you're logged in/out, or maybe that URL has a different token each day that makes it seem like a completely different URL, or...

▲

skydhash 5 hours ago | parent | prev [-]

> You hit that /issue command with "button should be yellow not red".

Wouldn’t it be easier to just open the inspector, find the css class, grep the source code, and then edit the properties? It could be even easier in an SPA where you just have to find the component file.

▲

bluGill 3 hours ago | parent | next [-]

If you are a web programmer sure. I write embedded code, I know all the things you are talking about in the abstract, but I'm not good at them because none of them have ever been relevant for anything I do. Give me a few hours and I can figure it out (maybe minutes, maybe days? - if you know this area your guess might be better than mine), but it isn't something worth my time.

there are a lot of people who are not programmers at all. I can teach my plumber everything you said (learning it myself is the easy part), but it will take years. In the end they just know "that button I'm pointing my finger at should be yellow not red". How to we transfer that pointed finger to a ticket is the question here.

	▲	skydhash 2 hours ago \| parent [-]
		> How to we transfer that pointed finger to a ticket is the question here. There’s a reason the Support and IT Technician role exists. They’re there for talking to the end user. And they in turn will write a proper report to Engineering. If you want to wear both hats at once, that is fine. If you want an agent to be your support middleman, that is also fine. But most LLM proponents are acting like it’s a miracle solution to some engineering bottleneck.

▲

xg15 4 hours ago | parent | prev [-]

> where you just have to find the component file.

This can be a substantial effort, especially if you're not familiar with the project.