Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
iba99
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Tara AI Is Hiring a senior back-end engineer to help build a ticketless future
(jobs.gohire.io)
1 points
by
iba99
4y ago
2.
▲
Tara AI Is Hiring for a growth lead to handle inbound and SEO
(jobs.gohire.io)
1 points
by
iba99
4y ago
3.
▲
Tara AI is building a smarter alternative to Jira and hiring a growth lead
(jobs.gohire.io)
1 points
by
iba99
4y ago
4.
▲
The workflows, culture and engineering process that drive 1500% YoY Growth
(gorelay.co)
1 points
by
iba99
4y ago
|
0 comments
5.
▲
by
iba99
5y ago
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 approa
6.
▲
by
iba99
5y ago
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
7.
▲
by
iba99
5y ago
Hey Mani! Great to see you here- it's been a while. You read our minds. We are thinking about how we can integrate with Jira for a truly sync'ed experience (since several teams have suggested using our interface to make updates in
8.
▲
by
iba99
5y ago
If you care to commit. Once version control permits. Bit by bit.
9.
▲
by
iba99
5y ago
Scrum-ptious (when a scrum goes really well)
10.
▲
by
iba99
5y ago
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
11.
▲
by
iba99
5y ago
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, wh
12.
▲
by
iba99
5y ago
Here's a few that didn't make the cut: The Dev files - the source code is out there Dancing with the git stars. (I could go on).
13.
▲
by
iba99
5y ago
Thanks giga, let us know how you get on with the platform as you start using it! We've thought about work hierarchy and how to create persistent states across the workspace with the universal drawer. It allows fast task, doc and subtas
14.
▲
by
iba99
5y ago
Thanks for reporting this! Please try a page refresh or typing in /logout and heading back to login again. This may happen with certain browsers or configurations - it's happening rarely so we still need to properly debug. Let us
15.
▲
by
iba99
5y ago
Hi folks, we launched to ShowHN over a year ago: https://news.ycombinator.com/item?id=23033387 Since then, we've continued to chip away at the problem of building responsive project management software, that syncs to G
16.
▲
Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
(tara.ai)
153 points
by
iba99
5y ago
|
96 comments
17.
▲
Tara AI (YC W15) Is Hiring a product designer to build the anti-Jira
(tara.ai)
1 points
by
iba99
6y ago
18.
▲
Tara AI (YC W15) is hiring a growth product manager to build an anti-Jira
(tara.ai)
1 points
by
iba99
6y ago
19.
▲
by
iba99
6y ago
Solid point, but I would counter that a feature or a product is never truly complete. The goal should be to get to a stage where users can derive value from the feature (or product), and ship. In our case, the main ask from developers is th
20.
▲
by
iba99
6y ago
We're a few months away from introducing Tara premium, which includes access controls for teams and user level permissions (ie contributor, etc), and is based on simple subscription based pricing. It's pretty much what our users h
21.
▲
by
iba99
6y ago
At it's core, we find it to be an Apple OS vs Windows OS problem. You can either build highly complex project management systems, with 50 different types of subsets, customizations and setup instructions (ie Windows?) or try to design
22.
▲
by
iba99
6y ago
Yep.
23.
▲
by
iba99
6y ago
In our experience building any form of meritocracy in recruiting, was excruciatingly difficult due to 1) inherent subconscious bias on the part of the recruiting team 2) pedigree bias - employers only wanting to view candidates that were f
24.
▲
by
iba99
6y ago
I think we would just integrate with an existing tool for this vs building it ourselves.
25.
▲
by
iba99
6y ago
On prem will take more time - but kanban and calendar views are on the roadmap.
26.
▲
by
iba99
6y ago
Nobody does. It's ridiculous that it takes 21 clicks to create a sprint. We've literally timed ourselves in every Jira instance (cloud and next-gen), and every point of configuration, setup or action just takes hours. A platform f
27.
▲
by
iba99
6y ago
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
28.
▲
by
iba99
6y ago
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.
29.
▲
by
iba99
6y ago
On the roadmap but looks like we should checkout WorkOS :)
30.
▲
by
iba99
6y ago
Not yet but it would form part of a future on-prem version of Tara, where privately-hosted instances of Github/Gitlab are accommodated.
More ›