31–40 of 83 posts
Earlier quoted context omitted.
I'm not sure how we can possibly be using the same website.
You're not. Jira is run over many different servers. I think that accounts for a great deal of the difference in experience. We self host Jira and it's not slow for us.
Given JIRA's ubiquity, I would strongly recommend that you build an integration that allows you to sync tickets from JIRA -> Zepel, so people can get the benefits of the Zepel interface without having to duplicate their work. (Unless this is already there, but I didn't see it on the website).
Earlier quoted context omitted.
You're not. Jira is run over many different servers. I think that accounts for a great deal of the difference in experience. We self host Jira and it's not slow for us.
I've just timed it on a bug detail page - it takes 7.8 seconds to complete with janky loading of different sections/data. I find it impossible to believe this is server related - looks more like they have terrible frontend code.
Earlier quoted context omitted.
this is really slick. any plans for an API for other integrations?
Thanks! Yes, an API is extremely high on my priority list. Zapier as well. Let me know what kinds of endpoints/actions you'd need from the API so I can make sure they are included. What integrations would you like to see?
Outlook integration would be nice as well. We used a simple jira plugin that would copy contents of email and make a task for a specific project.
just read through your license and it looks like buyers will be allowed to hack it to their liking +1
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…
I use JIRA cloud every day and have for almost 4 years and it's never been slow. Is your company using JIRA cloud or hosting your own?
JIRA (and confluence) are the slowest web apps I’ve had the pleasure of using. Simple navigation takes seconds when bouncing through pages. Accidentally clicking the wrong issue is physically painful. When I think JIRA I think glossy silver spinners.
I build WP sites for a local design agency (my client) who designs the theme for their client. I have 2-3 subcontractors that I work with to build these sites.
Building the site needs to be managed like a "project". Once launched, I want to give my client AND their client the ability to create tickets for any post-launch issues. I need these users to be "siloed" into organizations so that they can't see bug trackers for other clients. I need my subcontractors to be able to see tickets from projects they're approved to see.
I want the ability to create tickets via e-mail, sometimes from my client, other times directly from their client.
JIRA + Service Desk seems to give me everything I want, but the admin menus for their "classic" templates (i.e. Service Desk) are daunting. Lots of settings that (IMO) should be "global" are instead per-project. The only way to share these settings is to clone an existing project.
We've got ~12 sites that we're managing, and to make a "tweak" to one setting means having to go tweak that same setting 11 more times.
Is there any system smaller/simpler than JIRA that meets these needs?
The major selling point / complaint of Jira seems to be that it's too customizable. They're all different, and a bad manager can make your particular Jira instance unusable.
Is this one as customizable? Or is it inflexible? Or does it automatically "adapt" somehow? Does it assume that all teams work in the same way? I can't figure out what tradeoff it's making here.
The "JIRA Alternative" page says:
> "Because when you’re just a week away from shipping your feature, you should be tracking your entire feature. Not user stories and tasks."
which makes it sound like Zepel just picked a workflow. It "adapts" to you by assuming you already work in exactly the way it was designed.
Obviously there's a market for this as I think people are still chasing potential efficiency gains in making tools that are easy/fast/effective in organizing work, but as a product leader I don't see anything here that compels me to leave Github.
As someone running a software product team, we've made the decision to get as close to the developer process as possible with our product management tools. We've recently started doing everything in Github using Github projects, which honestly is really usable. It's kind of put me in a mindset where I'm not sure why I would ever pay for a separate product management tool as I can do most of my critical things with Gi…