Live data from Hacker News

Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events

tara.ai

91–97 of 97 posts

Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events

#91

Confluence is excellent. Jira is too slow and a big productivity brake. Tara seems interesting.

One other thing we've noticed is how slow Confluence and Jira are together. It's fascinating that stitching these products together under one Atlassian service (through acquisitions) hasn't served to provide a good or modern user experience.

We built our "define" feature to allow for spec'ing, and docs. And let's not forget how frustrating markdown is in confluence. We're working to really service markdown well in our text editor, and should have it released soon.

Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events

#92
post #81

Any integration with Notion on the roadmap? How do teams migrate from JIRA to Tara?

We just launched an API and should have a migration tool soon. Right now, it's typically a simple CSV import of issues, but the data mapping doesn't work too well with Jira's data. So far, it's been a trojan horse approach. A small team starts using Tara, enjoys the experience, and it starts to spread within the organization. Startups have been our bread & butter, but we also have small teams at larger enterprises using it.

The long game is to continue with the approach of allowing small teams to use Tara, and go under the radar for as long as possible.

As for Notion integration, yup, it's on the roadmap. Our integrations roadmap should get faster now that our restful API fully releases this week.

Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events

#93
post #69

i'm just going to throw out a few questions asking if features i wish these kinds of systems had are in here. maybe they are, and if they aren't, hopefully it's helpful! what is the workflow like for going from a commit id (ala git-blame) to all available discussion and context around that change? is there any sort of unified search through history that shows both changes and all discussion/context around them? (pull…

Thats something we're working on i.e most of our R&D goes here, we've been building up capacity on getting contextual data from the commits/PR's and possibly from slack too and then surfacing it as meta data as a first step. For example being able to identify questions, solutions, possible additions to documentation.

The aim is to eventually pass on that data or use it for smarter inference like catching duplicates, bug frequency, reintroduction of code and possibly identifying tech debt. Our vision has been to go ticketless, while we're supplying the tooling to make those tickets today, in the future contextual information from different systems could provide enough context to do that work.

Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events

#94
post #5

Why startups don't try to break this charge per user per month thing? Would be great to have products which would charge like $10 a month for up to 5 users or so... why so greedy and charge 10 per user? So, if small team of 5..10 people, at $8 a month per user, is like $100 a month for single service. And if startup needs like 5..10 different services to pay, it becomes like a pretty good amount for paying for differ…

Very simple; at the prices you cite, the largest charge is the one you forgot about: people hours needed to maintain and setup these services. 100$ sounds like a lot but it's only 1-2 hours of development time per month; less if you are in a competitive market. And lets face it, it's never just 1 hour per month. Just spending a week or so setting this stuff up could fund years of SAAS bills potentially in terms of ti…

I guess from the other sub thread below Self Hosting takes away alot of the liabilities of operating the software when you're small, atleast in the a very litigious US and Europe. Larger incumbents eventually have been moving away from that self hosted model to provide consistent service or layer on professional services for those that can afford it.

Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events

#95

Earlier quoted context omitted.

Can you define what data has to remain on Canadian servers? If it's just user data, and not your actual code, then you could use a synthetic data provider like https://synthesized.io to convert real user data to synthetic with similar properties, then host your code wherever you want.

Jira tickets (and Tara tickets) are going to have user data (including poorly-defined user requirements). Turning that into synthetic data with Synthesised will almost definitely lead to developers building software that does not match the original requirements.

If you have real user data in non-production systems (e.g., development JIRA/tracking system) you're already doing it wrong. At the firm I work at we scan all non-prod systems for user identifying data and flag it up for removal.

Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events

#96
post #74

Earlier quoted context omitted.

That's $70 a month, which seems high, but not extortionate given that it's meeting very specific requirements.

The very specific requirement of doing exactly the same thing you could do for a fraction of the price the year earlier: manage issues? Running software is not some exotic requirement.

> Running software is not some exotic requirement.

But running software in an environment you don't control, but where it's expected to run perfectly or else you're on the hook for the support, that is. On-prem services are hard to get right, there's all sorts of issues around things like upgrades, software versions, etc.

I get that it used to do this, but software gets updated and moves on. I think it's reasonable to expect that you can remain on an outdated version and old pricing scheme, but give up support after some period of time, but I could also understand companies not wanting to offer that.

Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events

#97
post #38

Earlier quoted context omitted.

Our security policy doesn't let us put confidential information into other people's hands unless they are willing to commit to the full value of damages from a breach on their side. It's a great question to differentiate sales critters: the new ones are sure that they can work something out; the middle ones are dubious; the experienced people chuckle and disengage politely.

Are any external suppliers stupid enough to agree to this? Isn’t it basically writing you an unlimited cheque if someone hosting your data gets hacked?

You find how much their data is worth, then take insurance out to cover it, and pass the cost along.
Post reply on HN