tegon

/blob/main/docs/quickstart.m... The oss/local-setup guide is entirely empty https://github.com/tegonhq/tegon/blob/main/docs/oss/local-se... The oss/deploy-tegon guide does not explain anything and the script it references seems out of date https://github.com/tegonhq/tegon/blob/main/docs/oss/deploy-t... I'm done looking at this project. I strongly recommend hiring the best engineer you can find as quickly as you can.

on your "Tegon Cloud". If you're really going to be open-source, you need to make some significant improvements before anyone would consider contributing. Some documentation on how to self-host would be a good start. Look at all the environment variables in this dockerfile — which ones are necessary to run this service myself? https://github.com/tegonhq/tegon/blob/main/docker-compose.ya... - If you're going to be "open source", the quality of your codebase and engineering skills is going to be a deciding factor in whether or not you get outside contributors. Consider writing actual descriptions in your pull requests, describing what you've done and why. Here's a PR picked at random — this is bad engineering work and does not encourage others to contribute. https://github.com/tegonhq/tegon/pull/114 My advice is that you drop the facade of being "open source", hire a designer, and do some actual user research to figure out where people are actually struggling with their ticketing systems. The features you're building (automatic title suggestion, thread summarization, and "find similar tickets") do not solve the problems that I have had with ticketing systems. They're small, potentially nice-to-have features that absolutely do not help me understand the core question for all engineering teams: who is doing what, how will they do it, why, and when will it be done.

about how project management and issue tracking would look 5-10 years from now. The current tools didn't match our vision, which excited us and started the journey of Tegon. We aim to build a tool where manual workflows are either automated or handled by AI. This tool will provide better context about a task to an engineer by smartly gathering data from all sources, helping teams with better prioritization. Tegon loads all the data from local (indexed db) thus making it super fast to load and navigate. We make all of this happen by real-time sync in the background. Tegon also uses AI to simplify the issue-creation process by automatically creating titles, suggesting labels and assignees and identifying duplicates. Tegon also simplifies the issue creation process from Slack, just apply an emoji to a Slack message and a tegon issue will be created making it easier for other teams to raise bugs or feature requests to engineering teams. We deeply value the feedback from this community and have spent the last month revamping Tegon's design based on the feedback from our last launch. We just got started and there's a lot more to come. We're eager to get more feedback and keep building. Let us know what you think in the comments :)

arter Summaries: Uses AI to generate concise summaries of issue activity, keeping you focused. - Natural Language Search: Filter issues with ease by simply typing in plain text. - Automated Triaging: AI saves time by automatically categorizing issues coming in triage What's coming next Tegon isn't stopping there. We're actively building features to: - Prioritization Powerhouse: Groom and prioritise unscoped requirements for efficient development (check out our GitHub issue for more details - Personal Section: A dedicated personal section containing My issues and My notes - Context Enricher Agent: Tegon Agent will flag issues with insufficient descriptions to prevent misunderstandings - Prioritisation Agent: Assist team leads in managing sprints by analyzing tasks, priorities, and bandwidth in real-time, suggesting adjustments for optimal workflow. [Coming soon] Key Sources Website - https://tegon.ai/ Demo Video - https://www.loom.com/share/b664b01e9b064a02be5791c12b77a107?... We Heard You! We appreciate your feedback on our previous design. We've spent the last month revamping Tegon's look and feel to provide a fresher look. Let's Build Together! We're eager to hear your thoughts and keep improving Tegon. Feel free to share your feedback in the comments below!