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

Show HN: Zepel, a Jira alternative for product teams

zepel.io

Post reply on HN
Print view View original

11–20 of 83 posts

Re: Show HN: Zepel, a Jira alternative for product teams

#11

Post by codegladiator »

gauthamshankar wrote: post #3
kopiblanca wrote: post #2

OP if you are creator of Zepel ,just wondering why you build something against giant,like Jira?

Hi there kopiblanca, One of the founders of Zepel here. We believe JIRA and most other project management tools have evolved from the core use case of issue tracking. While they might be great for tracking issues and ad hoc work items, when it comes to product development, bug tracking is only a part of the equation. We believe 2 key aspects make product/feature development different. - Unlike bug tracking, a feature…

Product teams don't hate JIRA. They love JIRA. Engineers hate JIRA. From your explanation, I still don't understand how this is different from JIRA (apart from the theme).

Re: Show HN: Zepel, a Jira alternative for product teams

#12

Post by atonse »

new_here wrote: post #8

Zepel looks great, a much cleaner and more pleasant experience than JIRA. Everyone uses JIRA because it's become synonymous with agile, so companies purchase and use JIRA to show that they're agile. In practice though, JIRA is ridiculously cumbersome and slow. It's time for it to be challenged. If you can market yourself as a simpler and faster way for agile teams to run projects, and deliver on that, then you'll pro…

That’s funny that people get JIRA to associate themselves with agile methodologies because theirs is one of the worst tools for it (in that the UI is this confusing herrendous mess). Whereas Pivotal Tracker feels a bit too “purist” in the other direction. Maybe this tool will feel somewhere in the middle?

Re: Show HN: Zepel, a Jira alternative for product teams

#15

Post by gauthamshankar »

rebelrexx858 wrote: post #9

the most important piece of jira for us is the API. How/When do you plan to have an open api that will assist in navigating issues through webhooks? (i didn't see it listed anywhere if you already do)

We are actively working on our API's and Webhooks. We should be getting a v1 out in the next couple of weeks.

Re: Show HN: Zepel, a Jira alternative for product teams

#16

Post by 23andwalnut »

rid wrote: post #14

Is there any chance this will be possible to self-host in future? That's a deal breaker for us.

I built a self hosted alternative to trello, basecamp, etc - http://duetapp.com

I wonder if it's suitable for your use case? And if not, what I'd need to add for it to be something you'd use

Re: Show HN: Zepel, a Jira alternative for product teams

#17

Post by dragonsh »

atonse wrote: post #12
new_here wrote: post #8

Zepel looks great, a much cleaner and more pleasant experience than JIRA. Everyone uses JIRA because it's become synonymous with agile, so companies purchase and use JIRA to show that they're agile. In practice though, JIRA is ridiculously cumbersome and slow. It's time for it to be challenged. If you can market yourself as a simpler and faster way for agile teams to run projects, and deliver on that, then you'll pro…

That’s funny that people get JIRA to associate themselves with agile methodologies because theirs is one of the worst tools for it (in that the UI is this confusing herrendous mess). Whereas Pivotal Tracker feels a bit too “purist” in the other direction. Maybe this tool will feel somewhere in the middle?

Try Taiga [1] [2] truly open source beautiful system supporting both kanban and scrum style development. It's very intuitive with beautiful cards based interface. It also support user story point poker to assign story points.

Indeed it can be projected directly on a wall screen to see a kanban board in real-time with customizable details.

Also with easy plugin system, it can extend to integrate with other system in company to automate various processes or customize to once liking.

[1] https://taiga.io/

[2] https://github.com/taigaio

Re: Show HN: Zepel, a Jira alternative for product teams

#18

Post by gauthamshankar »

craigharley wrote: post #13

Is there any way to import tickets (issues and pull requests) from Github?

Craig, we only have a Jira, Asana and Trello import for now. We will be releasing our API endpoints soon so you should be able to get your tickets from Github into Zepel using it.

Re: Show HN: Zepel, a Jira alternative for product teams

#19

Post by msla »

new_here wrote: post #8

Zepel looks great, a much cleaner and more pleasant experience than JIRA. Everyone uses JIRA because it's become synonymous with agile, so companies purchase and use JIRA to show that they're agile. In practice though, JIRA is ridiculously cumbersome and slow. It's time for it to be challenged. If you can market yourself as a simpler and faster way for agile teams to run projects, and deliver on that, then you'll pro…

The thing about Jira and Confluence which annoys me most is the fact it's possible to have useless combinations of permissions.

For example, in Confluence, there's a nested structure: Pages exist in spaces. Pages can have more restrictive permissions than the space they're in, so you can have a space with pages anyone can edit and pages only a select few can edit. Now for the annoying part: It's possible to have permissions to edit a page in a space without permissions to view pages in that space. Does the special permission override the general? Does it, Hell! Of course not! That set of permissions is useless, in that it doesn't allow you to do a damned thing!

It would be great if Atlassian packaged a sudo plugin with their software, so you could see what a given user could see and figure out what's going wrong. It would be great if Atlassian packaged an auditor in with their software to, at the very least, alert you to useless permission combinations. I know the first would infringe on one or more paid plugins, so that's not going to happen, but I don't think anyone has anything which solves the second problem.

Post reply on HN