Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Tara – A free Jira alternative, now with Gitlab

tara.ai

Post reply on HN
Print view View original

51–60 of 140 posts

Re: Show HN: Tara – A free Jira alternative, now with Gitlab

#51

Post by iba99 »

loufe wrote: post #50
iba99 wrote: post #2

Hi HN! We last crossed paths 6 months ago, when we shared Tara 1.0, a simple Jira alternative. https://news.ycombinator.com/item?id=23033387 I'm one of the creators of Tara, and with support and feedback from the community, we've been hard at work building this v1.5 release over 24 sprints and 500+ pull requests. Several of you asked for an improved Github sync, PRs and commits tracked in tasks, alongside a Gitlab in…

Any plans to accommodate privately-hosted git servers?

Not yet but it would form part of a future on-prem version of Tara, where privately-hosted instances of Github/Gitlab are accommodated.

Re: Show HN: Tara – A free Jira alternative, now with Gitlab

#53

Post by iba99 »

pj_mukh wrote: post #34
otabdeveloper4 wrote: post #10

This thing is in absolutely no way a Jira alternative. (YouTrack is the Jira alternative, but it's not free.)

We went from Jira to Tara (with Notion in the middle), and the problem is everyone thinks they need Jira, and a huge swath of people really don't. Jira is a complex product and those complexities are probably needed by some people. OTOH, Tara's simplicity is godsent, especially as a small team. The comparison makes sense to me.

Hey PJ! We've loved having Placenote on board. Hoping the new slack integration works well for you guys- if not just ping! FYI - notifications on sprint reports are shipping in 2 weeks.

Re: Show HN: Tara – A free Jira alternative, now with Gitlab

#55

Post by valcker »

iba99 wrote: post #32
eecc wrote: post #28

Does it have something like JIRA-1330? Because that’s what makes everything else in Jira a sorry kludge

What's your take on changing the status quo around unique task/issue ID's?

Why change something that works? It is much easier/faster to use short IDs than long user story titles.

Re: Show HN: Tara – A free Jira alternative, now with Gitlab

#56

Post by derektwong »

eecc wrote: post #46
iba99 wrote: post #32

Earlier quoted context omitted.

What's your take on changing the status quo around unique task/issue ID's?

Can't say anything more than: it depends. To its essence, an ID allows interested parties to track something over time. If you add additional meanings to an ID - e.g. the parent project as Jira does, or the kind as in ServiceNow - these can become outdated over time, and deceiving. I'd say it's ok to change the "external name" as this other metadata changes over time (project name, bug, task, story, whatever...) but…

Curious, do you mean: if a task was part of project ABC, with an ID of ABC-123, then if someone moved it into project DEF, its ID is now changed to DEF-621, those two should be linked, right?

Re: Show HN: Tara – A free Jira alternative, now with Gitlab

#58

Post by ZephyrBlu »

masukomi wrote: post #48
pj_mukh wrote: post #40

Earlier quoted context omitted.

FWIW, they explain exactly how they'll make money in the website (under Pricing) and in this thread.

we hope to get you dependent upon our product, and in the meantime come up with something we hope you'll be willing to pay for is not the most confidence inducing of business plans. Also, if the current plans are "free forever" have no caps on users or much of anything else and are good enough to use until they actually finish off the things worth paying for then how many folks are actually going to be inclined to pa…

The business model isn't anything special... It's just freemium.

Take a look at ProfitWell for instance, they do the same thing: Give away their core product then make money on upsells.

Also, building the business model as they go is pretty normal for a startup.

Re: Show HN: Tara – A free Jira alternative, now with Gitlab

#59

Post by syed99 »

viach wrote: post #43
serial_dev wrote: post #39

Earlier quoted context omitted.

How do you interpret this in the "Pricing" modal: > Our free forever plan has unlimited tasks, sprints and workspaces, with no user limits.

I interpret it as "we will somehow monetize your data and train our AI model on your activities"

Hey! Co-founder/CTO of Tara here.

We take privacy around your data very seriously. We're thinking about the ML training model as a "walled garden", ie recommendations are based on your past sprint activity, effort load, tasks completed during a sprint, etc. and are exclusive to your organization.

In the future, if we decided to do benchmarking (for eg quick recommendations on how companies in your industry are running sprints), we would have a double opt-in. This would mean anonymizing the data, and providing the recommendations an opt-in. Basically, very similar to how google's autocomplete email recommendations work.

Re: Show HN: Tara – A free Jira alternative, now with Gitlab

#60

Post by iba99 »

eecc wrote: post #46
iba99 wrote: post #32

Earlier quoted context omitted.

What's your take on changing the status quo around unique task/issue ID's?

Can't say anything more than: it depends. To its essence, an ID allows interested parties to track something over time. If you add additional meanings to an ID - e.g. the parent project as Jira does, or the kind as in ServiceNow - these can become outdated over time, and deceiving. I'd say it's ok to change the "external name" as this other metadata changes over time (project name, bug, task, story, whatever...) but…

One way we've tried to fix this is with our slack integration. Using the task URL, or ID, the integration quickly unfurls context in the task (showing story info) and allows quick actions. Same process with requirements/epics.

URL unfurling was shipped today with the slack app, and quick actions are coming in a few weeks.

Post reply on HN