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

Plane: Open-Source Alternative to Jira

github.com

Post reply on HN
Print view View original

151–160 of 238 posts

Re: Plane: Open-Source Alternative to Jira

#151

Post by fffrantz »

pfych wrote: post #116

I tried setting this up on my homelab via docker. Not only did it take ages to build, I found it really difficult to run it behind an already configured nginx instance, it seemed set on running its own one. There's an open ticket on the repo to improved the docker setup experience, I'll definitely be checking this out in a few months once its all be streamlined.

It seems ok with podman but I can never login using the default credentials. Build time was indeed pretty long as well, and throwing all kinds of errors. I think if you set it up with an IP address, it doesn't run an nginx container to front the whole thing.

Re: Plane: Open-Source Alternative to Jira

#152

Post by alkonaut »

MobiusHorizons wrote: post #95
ezekg wrote: post #90

Earlier quoted context omitted.

Why would you want to do that? I personally hate those “stale issue” bots on GitHub, and this sounds like the same.

Like it or hate it, there just isn’t enough time and energy to do all the things you might like to do. Triaging and prioritizing are usually best done manually, but “it hasn’t been worked on” is a cheap and acceptably accurate proxy for “not that important” for some teams.

Taking a bug report and making a good workitem might be a lot of work. If the same thing happens 2 years later you'd need to do the same work again if you already deleted the bug workitem. If the old stale bug ticket was still around you'd both have a) saved the work of writing it again because you would find it when searching and b) have a very good indication that the bug you are triaging might not be that serious because it has been seen before and not prioritized.

You could just automatically mark it "stale" or whatever instead of hiding it, which would give the best of both worlds. Automatic sunset for the item, without the duplicated effort.

Re: Plane: Open-Source Alternative to Jira

#153

Post by jpalomaki »

GuB-42 wrote: post #54
smallerfish wrote: post #4

I love seeing competition for Jira, because it needs to die, but I think you need to do a better job explaining your value prop. Your first bullet list of features doesn't really make it sound all that different. Why would I have a better time using this than Jira, bearing in mind that I'd be giving up custom workflows and probably a lot of integrations? (No shade intended. If you can answer that concisely, put that…

Is Jira that bad? It sure is a mess, but that's because its requirement are a mess. It is not SAP but that's the idea, something that sits between developers, testers, management, customers, etc... People who want different things, speak different languages, and somehow need to work together. If you just want an issue tracker, there are many options. Bugzilla, Mantis, GitHub, GitLab, Gitea,... Some of them customizab…

I think Jira is fine and it’s ok tool. Nowadays the performance of the cloud version also has been good.

BUT it is absolutely possible to configure Jira to be horrible to use. Add lot’s of extra fields, force complex workflows etc.

Re: Plane: Open-Source Alternative to Jira

#155

Post by bipson »

The Problem with Jira is not that it's dumb or too sophisticated.

The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you right now where the a lot of frustration arises.

In a similar vein, it wants to cater devs, coaches, POs, business people, customers and all of them over various orgs with drastically different workflows. Serving everyone equally must lead to a mediocre experience. You will always miss something, while there is so much stuff you don't need or want and you have to work around.

Arguably, this has become better a lot in the last 10 years, but you will always long for "something better".

But the most painful issue is that in some orgs Jira is the workflow, instead of supporting it and staying in the background. At some point people are only sending around ticket links, commenting on tickets, requesting people monitoring their queues. This creates overhead, redirection and Jira becomes a distraction you need to handle.

As a result Jira becomes a proxy for all the things going wrong with your daily work and a problem of its own.

Re: Plane: Open-Source Alternative to Jira

#156

Post by gghhzzgghhzz »

smallerfish wrote: post #4

I love seeing competition for Jira, because it needs to die, but I think you need to do a better job explaining your value prop. Your first bullet list of features doesn't really make it sound all that different. Why would I have a better time using this than Jira, bearing in mind that I'd be giving up custom workflows and probably a lot of integrations? (No shade intended. If you can answer that concisely, put that…

I've used it as a stand in workflow/case management tool in dev and production apps a few times. e.g. when presented with a lot of detailed requirements on case management from product managers, and knowing at an early stage they are far too detailed to stand up to the reality of being used in the business, I've argued for simply creating a new project in an existing well-speced Jira instance with minimal workflow, taking that live as a prototype and modifying the workflow later, possibly with the goal of getting better specs for replacing it with something custom-built.

As a development tool for stories / tasks and bug tracking I don't enjoy it.

Re: Plane: Open-Source Alternative to Jira

#157

Post by contravariant »

viharkurama wrote: post #21
smallerfish wrote: post #12

Earlier quoted context omitted.

Check out Youtrack - not open source, but free if you have 10 or fewer users.

Youtrack is great but complicated with it's UX. Code level extensibility with Project management tools is near zero. We are working on our extensibility framework called Propel, it gives you the ability to write code with React to extend Plane. Open-sourcing in Q3 2023.

That's a bit unfair towards youtrack, you can extend its behaviour with arbitrary javascript. It's not the cleanest development experience I had but it is powerful.

Unless I'm misunderstanding what you mean by "code level extensibility".

Re: Plane: Open-Source Alternative to Jira

#158

Post by zelphirkalt »

bipson wrote: post #155

The Problem with Jira is not that it's dumb or too sophisticated. The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you right now where the a lot of frustration arises. In a simila…

Catering to many different kinds of people explains some of the bad stuff, but it does not explain, why seemingly every single Atlassian product including Jira sucks at parsing Markdown or supporting Markdown well. In the big picture maybe some things suffer from catering to too many audiences, but in the small, it is just lack of good engineering. Basically any markdown parser you can install at no cost and even with pushover license for any popular programming language works better than what they cobbled together. Is it a case of some "senior" person sitting somewhere sheltering their brain child?

Also they seem to be immune to feedback, which they wanted to collect in Confluence, using some popups.

Re: Plane: Open-Source Alternative to Jira

#159

Post by raverbashing »

bipson wrote: post #155

The Problem with Jira is not that it's dumb or too sophisticated. The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you right now where the a lot of frustration arises. In a simila…

I agree these are issues

But having a jquery frontend experience with a single-threaded backend system doesn't do it any favours ;)

Post reply on HN