Show HN: Tasquery – No-login bridge from messy notes to Jira tickets
1 points
1 hour ago
| 1 comment
| tasquery.com
| HN
jirigalis
1 hour ago
[-]
I built Tasquery to solve the "Documentation Tax" - that tedious 20-minute refactoring of messy Slack threads and meeting notes into structured Jira tickets after the actual work is done.

The Approach: I initially over-engineered the settings, but early feedback was clear: devs just want to get back to coding. I pivoted to a "Zero-Friction" flow. No signup, no onboarding, no sliders. You paste the chaos, you get a structured draft.

Technical Details: It uses gpt-4o-mini with enforced JSON mode for strict technical structure. I recently added "Magic Actions" - one-click buttons to refine the draft (adding edge cases or QA steps) without manual prompting.

The Latency Trade-off: Full disclosure: The API takes about 15-20 seconds. I’m currently prioritizing deep context analysis over raw speed. I'm looking into streaming the response next to improve the perceived performance.

Privacy: Stateless by design. No data is stored; everything is processed in-memory.

I’d love to get your thoughts on the UX and the quality of the generated tickets.

App: https://tasquery.com

reply