What evidence do you have that suggests auto-generated titles are better?
Show HN: Tegon: Open-source alternative to Jira, Linear
41–50 of 133 posts
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#42Earlier quoted context omitted.
All the data is there, you just need to connect to it with a new class of BI tool. It's coming.
That's missing the point. The root comment is asking for a different product (one that integrates with Jira) than the one offered by the op (one that replaces Jira). The manner in which such a product would exist isn't the concern of my argument.
That's not how I read it, but I don't see any case where offloading the entirety of IP in Jira to a third party makes any sense.
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#43IMO the absolute most important thing with a tool like this is performance. I have to sign in to a handful of cloud desktops each week and interact with customer Jira/Confluence/AzureDevOps/etc pages, and the big thing which kills my engagement is the app not being snappy enough. Doesn't matter how many of the features our Agile SAFe scrum wizard wants me to use, I'm not going to bother if there is too much friction. These apps inevitably require a lot of clicks, so latency becomes very noticeable.
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#44If you are planning to monitise it through SaaS, might be worthwhile to change the license to AGPL from MIT.
AGPL doesn't prevent anyone from taking your code wholesale and hosting the entire thing. They didn't make any changes so they don't have to contribute anything back per AGPL. OP can make any part that interacts with it, such as billing and infrastructure code, closed source as they are the copyright holder and thus do not have to abide by AGPL or any license themselves. If they make every contributor sign a CLA, the…
If you build something interacts over a network with an AGPL’d program, then you are hitting the distributing over a network clause in the license.
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#45If you are planning to monitise it through SaaS, might be worthwhile to change the license to AGPL from MIT.
Thank you for your suggestion. You’re absolutely right; we are actively exploring licensing options, including AGPL, to ensure that our product remains protected. We value input from the community and are open to suggestions and assistance in making this decision. Our goal is to prevent unauthorized copying and resale of our product under different names while fostering a collaborative and innovative environment.
You can also expressly state that you have a commercial license too. Your entire license can be something like “ If you’re using it for commercial purposes, you must see a commercial license with XYZ. Otherwise, for all noncommercial uses, you may use the software according to the terms of the AGPL license.”
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#46Would it be possible to run AI/ML on an existing jira/github large project (k9mail/KDE(gitlab) and show/prove this can be useful/better etc? Thanks
If you are suggesting OP do this to demonstrate that their assertion is correct - that AI generated issue titles are objectively better - this is a Good Idea.
I have to guess /hope that they did this already; who would make a time investment like this without first proving that the product has value? Anyway I certainly wouldn’t even pilot it without some proof.
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#47What evidence do you have that suggests auto-generated titles are better?
We thought auto-generated titles could make life a bit easier. Creating the perfect title for every task can be tricky, especially when things get complicated. So, we added this feature to help with that. (This is also something I faced as a challenge while I was working in Airbyte the community does a great job at explaining the issues but we always have to edit the title to make it more crisp.)
Right now, we’re using the product ourselves and trying it out with a few customers. We’ve noticed that for simple placeholder tasks, a straightforward title works just fine. But for more detailed tasks with longer descriptions, the auto-generated titles seem to work better. We’re still experimenting and gathering feedback to make it even better.
Examples from our board:
Description: - utils.py 228 : Failed to call LLM with the following error: BedrockException Invalid Authentication - An error occurred (UnrecognizedClientException) when calling the InvokeModel operation: The security token included in the request is invalid.
Title: Feat: Investigate Salesforce cloud version error: Invalid Authentication
Description: Triage ux bug - once i decline or accept a triage request, it re-directs me to issues screen. Ideal behaviour to be at the triage list view where you either show removing it from triage or highlighting that an action have been taken on this request.
Title: Redirect user to Triage List after Accepting/Declining Request
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#48IMO the absolute most important thing with a tool like this is performance. I have to sign in to a handful of cloud desktops each week and interact with customer Jira/Confluence/AzureDevOps/etc pages, and the big thing which kills my engagement is the app not being snappy enough. Doesn't matter how many of the features our Agile SAFe scrum wizard wants me to use, I'm not going to bother if there is too much friction.…
True performance is our priority. From the very beginning, we focused on ensuring that our app ran smoothly and quickly. To achieve this, we load all the data locally, allowing you to experience everything at lightning speed. Our background server keeps your data synchronized seamlessly between the server and the client, so you get the best of both worlds: speed and reliability.
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#49IMO the absolute most important thing with a tool like this is performance. I have to sign in to a handful of cloud desktops each week and interact with customer Jira/Confluence/AzureDevOps/etc pages, and the big thing which kills my engagement is the app not being snappy enough. Doesn't matter how many of the features our Agile SAFe scrum wizard wants me to use, I'm not going to bother if there is too much friction.…
We are also working on a more chat-based approach to interact with the tool. To let you directly handle things from the messaging tools like slack.
Re: Show HN: Tegon: Open-source alternative to Jira, Linear
#50What evidence do you have that suggests auto-generated titles are better?
We thought auto-generated titles could make life a bit easier. Creating the perfect title for every task can be tricky, especially when things get complicated. So, we added this feature to help with that. (This is also something I faced as a challenge while I was working in Airbyte the community does a great job at explaining the issues but we always have to edit the title to make it more crisp.) Right now, we’re usi…
Lack of "crispness" in user titles is a tooling problem?
Isn't this "wrinkly" technical detail lost?