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

Show HN: Tara – A smart and free alternative to Jira

tara.ai

Post reply on HN
Print view View original

101–110 of 182 posts

Re: Show HN: Tara – A smart and free alternative to Jira

#101

Post by adrianmsmith »

iba99 wrote: post #21
siphor wrote: post #9

why the ai tld?

Our first version (which failed miserably) was a prediction-only product with no workflow and a minimal interface. Here's what happened: - Initially our hypothesis was we could build data models that automatically suggested a specification or tasks based on certain criteria the user identified (for e.g. iOS app for video based calling). - The system would suggest programming languages, frameworks and a set of tasks b…

Do tell us the story of the tara.com domain negotiation some time!

Re: Show HN: Tara – A smart and free alternative to Jira

#102

Post by asarkar »

alkonaut wrote: post #96

One thing that bugs me with development workflow tools is how they never really integrate with the true workflow of developers. Once you have a development workflow with Pull Requests, Code reviews, QA etc, it would be nice to be able to encode it into the What's the true progress of an issue (ticket, work item...)? Why do I need to remember to set a ticket to "resolved" after a PR completes, and so on. Every place h…

https://linear.app is your answer here

Re: Show HN: Tara – A smart and free alternative to Jira

#104

Post by kot-behemoth »

alkonaut wrote: post #96

One thing that bugs me with development workflow tools is how they never really integrate with the true workflow of developers. Once you have a development workflow with Pull Requests, Code reviews, QA etc, it would be nice to be able to encode it into the What's the true progress of an issue (ticket, work item...)? Why do I need to remember to set a ticket to "resolved" after a PR completes, and so on. Every place h…

Have you heard about Basecamp's solution to this, Hill Charts (https://basecamp.com/features/hill-charts)? It's definitely not an 'enterprise' solution, but I find its simplicity a really good map for the _true_ workflow of developers. That is to say, it's abstract and simple enough to use for devs, while meanigful enough for managers to gauge progress.

Plus, their writeup on imagined vs discovered tasks and how Jira et al give false sense of control when creating tickets upfront is also illuminating: https://basecamp.com/shapeup/3.4-chapter-12

Re: Show HN: Tara – A smart and free alternative to Jira

#105

Post by all_iv »

congrats on the release! I tried a little bit and this looks nice. I like the focus on agile workflow so that people can quickly evaluate whether this is suitable for them. Liking it so far!

although I seem to have a problem searching for task inside my requirement details

Re: Show HN: Tara – A smart and free alternative to Jira

#106

Post by swiley »

alkonaut wrote: post #96

One thing that bugs me with development workflow tools is how they never really integrate with the true workflow of developers. Once you have a development workflow with Pull Requests, Code reviews, QA etc, it would be nice to be able to encode it into the What's the true progress of an issue (ticket, work item...)? Why do I need to remember to set a ticket to "resolved" after a PR completes, and so on. Every place h…

I’d personally be happier with less integration.

Tickets are for people not machines, they’re used to communicate with the team/PM. All the information in the ticket comes from people (usually developers) anyway. There’s no way for a machine to know if the content of a PR truly represents what the ticket asked for or what the actual status of the ticket is.

I think the only time I’ve ever used kanban in the original form was in college robotics but my understanding is that these tools are supposed to replace sticky notes.

Re: Show HN: Tara – A smart and free alternative to Jira

#107

Post by anentropic »

bberenberg wrote: post #31
beart wrote: post #7

Looks awesome and I would love to try it out. Unfortunately I work at a large company which has 'standardized' on Jira + other related tools. Now that the majority of work is being done through Jira, it would take a world ending event to move away, no matter how good of a product the alternative is.

Disclaimer: I run an Atlassian consulting company. In most scenarios I run into, "Unfortunately I work at a large company which has 'standardized' on Jira" translates into "Someone set up Jira poorly and now we dislike using it". The thing is that if you replace Jira with any tool you can imagine, the statement will hold true. Jira isn't inherently a better or worse tool than most others out there. If you're at an or…

As a user (ignoring fixable things like our admin set up a state-machine for tickets so you can't move story more than one state at a time...) I mostly just hate that the UI is slow and I can't use Markdown like I can in GitHub and Slack

Re: Show HN: Tara – A smart and free alternative to Jira

#108

Post by wes-k »

alkonaut wrote: post #96

One thing that bugs me with development workflow tools is how they never really integrate with the true workflow of developers. Once you have a development workflow with Pull Requests, Code reviews, QA etc, it would be nice to be able to encode it into the What's the true progress of an issue (ticket, work item...)? Why do I need to remember to set a ticket to "resolved" after a PR completes, and so on. Every place h…

https://clubhouse.io/ does a decent job at this. I don’t need to mark in progress (branch created), in review (pr open), or done (pr merged).

Re: Show HN: Tara – A smart and free alternative to Jira

#109

Post by azmenak »

alkonaut wrote: post #96

One thing that bugs me with development workflow tools is how they never really integrate with the true workflow of developers. Once you have a development workflow with Pull Requests, Code reviews, QA etc, it would be nice to be able to encode it into the What's the true progress of an issue (ticket, work item...)? Why do I need to remember to set a ticket to "resolved" after a PR completes, and so on. Every place h…

We use JIRA to track our product development with a fairly large team (including 17 engineers) and while JIRA has its pain points, it does have integrations with development workflow.

In our setup, after a PR is merged in Github, the ticket automatically moves to the next “step”, in our case “Ready for QA”.

Beyond that there are automation workflows that accomplish much of what you are asking for here, the issue is that these are complex tools/flows that require a lot of up-front work and continuous maintenance which might not be worthwhile for all teams.

Re: Show HN: Tara – A smart and free alternative to Jira

#110

Post by beart »

anentropic wrote: post #107
bberenberg wrote: post #31

Earlier quoted context omitted.

Disclaimer: I run an Atlassian consulting company. In most scenarios I run into, "Unfortunately I work at a large company which has 'standardized' on Jira" translates into "Someone set up Jira poorly and now we dislike using it". The thing is that if you replace Jira with any tool you can imagine, the statement will hold true. Jira isn't inherently a better or worse tool than most others out there. If you're at an or…

As a user (ignoring fixable things like our admin set up a state-machine for tickets so you can't move story more than one state at a time...) I mostly just hate that the UI is slow and I can't use Markdown like I can in GitHub and Slack

I had the same "state machine" style workflow with something like 6 steps in it. Combined with the slow load times and clumsy interface, I once calculated that it would take me several hours just to move all of my assigned tickets at the time from state 0 to state 5. Fortunately I was able to switch to a workflow that made more sense.

I feel the two types of problems you mentioned form a feedback loop, each making the other more painful.

Post reply on HN