Any integration with Notion on the roadmap? How do teams migrate from JIRA to Tara?
Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
81–90 of 97 posts
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#82Can I self-host it? The only reason we're going to move away from JIRA is that Atlassian dropped server installs and is moving everyone to their cloud or datacenter products. Have a great conversion from JIRA and a reasonably-priced self-hosted option, we'll be looking at you in six months.
Its definitely something we've been exploring when putting our product roadmap together. I'm curious though, if we had a private cloud instance vs self hosted? I'd love to understand why self hosted would be the option you'd go for.
I think for most/many European companies, especially those that are potentially handling PII, there are regulatory concerns with using US based hosting/companies.
My employer for instance has put a ban on deploying anything new on AWS/Azure/Google Cloud until legal issues have been settled after Privacy Shield was invalidated.
Everything new right now needs to be on EU/EFTA data centers run by EU/EFTA companies. This essentially means self hosting since most clouds are owned by US companies.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#83Earlier 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.
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.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#84Earlier 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?
This is actually a fairly big deal in enterprise sales. I learned that one of the reasons my company didn't use Slack and opted for a larger company's (arguably inferior) clone was that Slack was basically not suable (blood from a stone and all that). My company basically wanted the ability to hold the provider liable for a breach. I look around at our other vendors and most of them appear to be capable of weathering a lawsuit, whereas Slack (at that time) was not. Now...however....things have changed. :)
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#85The 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.
Scrolling is very laggy in Firefox.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#86Earlier quoted context omitted.
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.
The on-prem requirement; probably most paying users with that requirement are not very price sensitive, since it's a regulatory requirement on them, or similar. They're also probably typically large orgs (so it doesn't look so expensive per user, if they would even consider it in those terms), and resistant to switching providers due to other requirements/processes anyway.
I choose the 50 users example for a reason: I know plenty companies in that kind of size that prefer self-hosting and are looking to replace Jira now.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#87It's hard to tell if it's it integrated with Git directly or only via Github & Gitlab! Both Github and Gitlab have built-in project management features! Why should I use a different tool if I'm using Github/Gitlab?
With GitHub we sync all the issues in real time. So all changes you make in Tara reflect on GitHub issues too. We make it easier for larger teams who run sprints and require a more accessible interface work better together i.e designers, PMs and EMs.
For the Gitlab for the time being we only allow connection of issue tickets to MRs and some organized views of commits and MRs in our progress mode.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#88Earlier 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…
Primarily, you just look at this as a cost of the person's salary.
$10 / person as a standalone fee seems very different than...
$X,000 / month salary + benefits + $10 / month for a service that helps them get more done with their time that you're paying for.
Totally agree about guest contributors though. IMO ClickUp.com has the best pricing model of the bunch for this type of thing.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#89Confluence is excellent. Jira is too slow and a big productivity brake. Tara seems interesting.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#90Earlier quoted context omitted.
The on-prem requirement; probably most paying users with that requirement are not very price sensitive, since it's a regulatory requirement on them, or similar. They're also probably typically large orgs (so it doesn't look so expensive per user, if they would even consider it in those terms), and resistant to switching providers due to other requirements/processes anyway.
I choose the 50 users example for a reason: I know plenty companies in that kind of size that prefer self-hosting and are looking to replace Jira now.
And that sucks, I do understand, I just don't think Atlassian will feel the loss, and stands to gain far more by jacking the price for the price insensitive customers who remain, as above.