Live data from Hacker News

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

tara.ai

41–50 of 97 posts

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

#41

Any plans of supporting kanban boards in future? We find that kanban works very nicely to manage certain types of projects, and we're currently using Jira's kanban features for many projects. I'd love to see alternatives. Sync'ing with self-hosted Git servers would be good to have. Many of our projects are hosted on Git servers in a "secure network" behind a corporate VPN that, for legal and commercial reasons, canno…

We do plan on supporting kanban views over the next few months. It’s a WIP along with list views.

The question about self hosted git servers, we do support them but not officially through the GitHub app which is on the App Store. We do have a fully compatible backend that can integrate with any self hosted git using webhooks, we haven’t exposed those to users as of yet.

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

#42

I looked but can't see in the FAQ or anywhere - do you provide a way to migrate from Jira and do you integrate with bitbucket?

Hi there, we currently don’t have a bitbucket integration but it’s on our roadmap towards the end of the year. We will however be updating our migrate tools early Q4 with Jira/Confluence mapping.

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

#43
post #35

The website is super slow for me, which doesn't feel like a good thing.

Sorry to hear that, we just migrated hosts, our page FCP and speed index was around 3 seconds but if that’s not what you experienced, we’re definitely going to take a look into it.

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

#44
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…

Offering a similar product at lower pricing is usually the worst-way to compete unless it's a major disruption (free, different business model, etc). You might help a few small customers but you'll end up missing on most of the revenue that your competitors are capturing. While bills do add up, you should only be paying for services if they're delivering more value then the price you're paying.

That’s how we see it too. We didn’t underprice it to simply compete, it’s a mix of how the actual tech is built and how we can keep our net costs per user low. We’re just curious and love to hear how users perceive pricing and want to facilitate a conversation. The major value prop here is around automation; reducing engineering time in manual status updates in tickets and high value actions like assignment or effort prediction.

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

#45
post #41

Any plans of supporting kanban boards in future? We find that kanban works very nicely to manage certain types of projects, and we're currently using Jira's kanban features for many projects. I'd love to see alternatives. Sync'ing with self-hosted Git servers would be good to have. Many of our projects are hosted on Git servers in a "secure network" behind a corporate VPN that, for legal and commercial reasons, canno…

We do plan on supporting kanban views over the next few months. It’s a WIP along with list views. The question about self hosted git servers, we do support them but not officially through the GitHub app which is on the App Store. We do have a fully compatible backend that can integrate with any self hosted git using webhooks, we haven’t exposed those to users as of yet.

Thanks for the response, though my question was more about whether you've thought through how your webhooks based approach can work through VPNs.

For example, one of the organisations I work with uses a CheckPoint capsule VPN with some non-standard configuration that's controlled by their IT department that manages and supports client workstations.

To even access the Git server requires the user to be connected through VPN. I suppose you'll need Tara to follow the same route to the Git server that's sitting behind this VPN, right? This would be quite a different story than having Tara connect to a public facing self-hosted Git server, e.g., on our own data center or on AWS.

I suspect this will he a hard (impossible?) problem to solve unless Tara itself goes self-hosted and is on the same VPC as the Git server behind our VPN.

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

#46
post #41

Earlier quoted context omitted.

We do plan on supporting kanban views over the next few months. It’s a WIP along with list views. The question about self hosted git servers, we do support them but not officially through the GitHub app which is on the App Store. We do have a fully compatible backend that can integrate with any self hosted git using webhooks, we haven’t exposed those to users as of yet.

Thanks for the response, though my question was more about whether you've thought through how your webhooks based approach can work through VPNs. For example, one of the organisations I work with uses a CheckPoint capsule VPN with some non-standard configuration that's controlled by their IT department that manages and supports client workstations. To even access the Git server requires the user to be connected throu…

Thanks for clarifying. Yes this would be fairly different and requires an extra layer or configuration on our backend. You’re absolutely right about following the same route to the server per user and since our current configuration allows a workspace level workflow, we would have to write some middleware to handle this use case.

You are absolutely right about a self hosted solution being the better workaround which means it resides on an internally accessible network where the setup experience would be much more seamless.

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

#47
post #26

Earlier quoted context omitted.

This is the correct answer.

I guess if you assume that "small teams" are all working 100% on the one project... which isn't even slightly reasonable (hell: that isn't even reasonable for large teams). The per-user thing essentially means you are paying costs constantly for people who just need access to something as a contributor even though they are using it once a month. It is incredibly frustrating having to be like "ugh, I contracted with s…

One way to work through this would be to provide viewer vs collaborator user types - but ofc a viewer wouldn't be able to actually create tickets. The true goal is to build a system where everyone is productive as soon as they join, where a $5-$8 cost seems incremental, vs the work the system is able to augment for a full-time developer, business person or a contractor. This is why we're designing Tara to initially be an interface in terms of user interactions, but over time, to augment work as it happens. We've started down this path with effort predictions, sprint loads and automation of statuses.

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

#48
post #29

Earlier quoted context omitted.

I don't believe they mean they're using git as the data store for the application. Sync with git means updating tickets based on parsing action commands embedded in commit messages pushed to your git server. Jira can actually do this, too, though I think you need to be using Bitbucket as your git server.

You do not need to use Bitbucket, works with Github too.

Here are the issues though with Jira's Github integration: 1- Requires unito or an additional plugin to truly function 2- Needs quite a bit of setup to get minimal value 3- No built-in dashboards optimized for git events (ie when is a PR merged, predicted vs actual, how does that relate to your team's current sprint). 4- One-directional sync (vs a true bi-directional sync).

We've optimized for built-in dashboards, minimal setup and a bi-directional sync. Over time, we're also going to be building inside the terminal or inside Github's interface, to truly enable seamless interactions with Git.

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

#49
post #30

Earlier quoted context omitted.

In our case it's due to regulations in place. For example, our data must stay on Canadian servers at all times.

Makes a lot more sense now, the flexibility to configure to your own resources for regulatory reasons.

You'll probably also encounter people who are a bit jaded after their experience with Jira's hosted cloud versus on-prem. Jira on-prem can be slow also, but at least you can throw ridiculous amounts of hardware at it and make it okay-ish.
Post reply on HN