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…
Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
51–60 of 97 posts
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#52I'll echo some of the other comments here that most of the bigger companies I've worked with want a better JIRA but are weary of smaller companies, data security, and the switching costs involved.
Is there a way to offer this on top of the existing Atlassian tools? A similar model would be something like Scratchpad for Salesforce: https://scratchpad.com/
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#53Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#54Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#55Earlier quoted context omitted.
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.
Eventually we caved and pushed their account execs to support a “secure” private cloud that passed our IT teams compliance criteria. Fun times!
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#56Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#57Earlier 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…
Other explorations we did were around finer grained permissions or a collaborator vs assignee. The reason the industry itself is geared towards seats based plans in the is to drive better revenue predictability and handle cost variability between free and paid users better but we’re seeing more and more creative changes to sass billing models.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#58Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#59Congrats on the new launch Iba and Syed, I still remember meeting you guys years ago in LA, you've come a long way! I'll echo some of the other comments here that most of the bigger companies I've worked with want a better JIRA but are weary of smaller companies, data security, and the switching costs involved. Is there a way to offer this on top of the existing Atlassian tools? A similar model would be something lik…
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 Jira + since we have simple built-in dashboards it just makes it easier to use for everyone). The challenge is to design it in such a way, that you don't have to spend a ton of time configuring the integration, mapping fields or needing a dedicated engineer for setup. We're on it - in the meantime would love to hear your feedback if you get the chance to try out Tara.
Re: Show HN: Tara 2.0 – Fast Jira alternative with automation based on Git events
#60We use JIRA and GitLab at work. In the GitLab CI/CD configuration we define a few hooks that update JIRA task status on various events (MR is created, MR is merged, etc). It's a bit of manual work but it's working flawlessly for years. How is it different from this offer?