gauthamshankar

No @iblaine, no one from Zepel created this website. Noticed that we were getting some traffic from this source and found this page.

Co-founder of Zepel.io [0] here. Thank you for giving Zepel a shoutout in the Jira alternatives section of the landing page. Would love to get feedback from the community regarding our App.

[0]:https://zepel.io/

Hi Hacker News!

I’m Gautham, one of the founders of Zepel (https://zepel.io). Last year we launched Zepel on HN and we got a tremendous amount of feedback and as well as our first bunch of paying customers.

Over the past year, based on the conversations with our users, we have been fine tuning the product and filling the missing functionality gaps.

While talking to our users we realised one of the biggest pain points with building software products is deciding what to focus on next. Yet the end users of your product are providing those very signals through multiple customer facing tools that your organisation uses. We felt that to answer this question effectively teams need the ability to get data from multiple tools that they use such as Intercom, Zendesk, Canny, Github Issues, etc to prioritise and plan work.

That’s why we have launched a new aspect to the product called Zepel Streams.

Streams lets you consolidate customer feedback, feature requests, bug reports, and even internal requests from several sources, prioritize, and align your teams on the desired outcome.

As a part of this launch, our tracking & execution side of the product will be renamed to Zepel Squads.

We would love to get your feedback on Zepel! Thank you.

Hi Hacker News!

I’m Gautham, one of the founders of Zepel (https://zepel.io). Last year we launched Zepel on HN and we got a tremendous amount of feedback and as well as our first bunch of paying customers.

Over the past year, based on the conversations with our users, we have been fine tuning the product and filling the missing functionality gaps.

While talking to our users we realised one of the biggest pain points with building software products is deciding what to focus on next. Yet the end users of your product are providing those very signals through multiple customer facing tools that your organisation uses. We felt that to answer this question effectively teams need the ability to get data from multiple tools that they use such as Intercom, Zendesk, Canny, Github Issues, etc to prioritise and plan work.

That’s why we have launched a new aspect to the product called Zepel Streams.

Streams lets you consolidate customer feedback, feature requests, bug reports, and even internal requests from several sources, prioritize, and align your teams on the desired outcome.

As a part of this launch, our tracking & execution side of the product will be renamed to Zepel Squads.

We would love to get your feedback on Zepel! Thank you.

Thank you for the feedback. We are working on the multi-select functionality in boards, alternatively, you can multi-select items inside a list or feature and move them to other boards. We understand it can be a bit hard without it while organizing an imported project and we will add the functionality soon. Regarding the auto-complete its something that should be working. Will take a look at it.

Agreed, the post-import experience has a lot of room for improvement and we are constantly iterating on it.

We have an import option while creating a project that will allow you to migrate your data from Jira to Zepel.

We have an export option available. You can download an HTML, text or JSON dump of your data. We will also be releasing our public API's soon, so you can use that to export your data anytime.

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.

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

Neal, we see Zepel being bought bottom up. We are engineers ourselves and we built a tool that we would be happy using. We also plan on having a data sync with Jira mainly to help teams within larger org switch to Zepel, while the updates still flow back to JIRA without breaking the “managements” view.

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 needs to be conceptualized and the form-based interface of these tools make it ridiculously difficult to spec out the requirements for a feature.

- Shipping a feature involves multiple disciplines and rarely follows a single fixed workflow.

Our approach to solving these two problems is,

- A text editor like interface that lets you specify your features and making it super simple to change or update items.

- Multiple boards per project to capture every discipline and the flexibility to move items across these boards as per your use case.

We believe its painfully hard for product teams to plan and ship features using JIRA and that's why we have created Zepel.

We have built a lightweight alternative to JIRA - https://zepel.io

Our primary focus is to help product teams plan and track their features. We support bug tracking and cross-functional collaboration as well.

It's under active development. Check it out and let me know your thoughts.