Live data from Hacker News

Plane: Open-Source Alternative to Jira

github.com

231–238 of 238 posts

Re: Plane: Open-Source Alternative to Jira

#231
post #122
post #54

Earlier quoted context omitted.

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…

jira-1369 is a 20 year old bug of email notifications not being put into a digest and instead flooding users. I for one feel like I grew up those people and we should share our wedding and other milestone photos and announcements on that chain.

Even though I’ve come to like Jira there are a few of these 15-20 year bugs that are just frustrating beyond belief. And a Jira PM will duck in there every 8 years or so to say they’re not considering it and then run away. Mine is how it’ll let you create infinite case variations of Labels, even though Labels are case-insensitive when querying, but it means the accidental variations people will make crap up the autocomplete forever.

Or the fact that Components or Versions can’t exist across multiple Projects. Thankfully we did basically automate Version management using their Automations to basically fake it. Thankfully Versions in JQL are searched by string instead of being instantly converted to ID like Sprints are.

Re: Plane: Open-Source Alternative to Jira

#232
post #214
post #210

Earlier quoted context omitted.

I don't know, I've seen that extreme, but I've also seen the other extreme. People with vast knowledge of JIRA, obviously far more than anyone else in the org, developing vast dashboards and labeling systems. Every ticket has to be properly groomed and properly built (even if not useful). That isn't always better.

Knowledge doesn’t equal expertise. JIRA has a very simple initial onboarding story, especially in comparison to servicenow or SAP. But it’s got a lot of hidden complexity that can make it super powerful. That power can become its downfall if implemented badly. Vast dashboards and labeling systems is improper implementation.

True, and worse, this kind of approach sounds like expertise. I've found some people are amazingly good at selling continuously expanding complexity of management overhead.

Re: Plane: Open-Source Alternative to Jira

#233

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 love seeing competition for Jira, because it needs to die I think when I die in ~50 years that HN will still be filled with stories ragging on Jira, or whatever it is that eventually replaces it. It's like the pastime that will never end. To be clear, I think it's great to see open source projects like this, and I think increasing competition is a really wonderful thing. I also totally agree that Jira has lots of…

Hi there,

This is Nitin from Plane. Your;s is an interesting take on project management tools. Quite understandably, no one can go out and try to solve everyone's problem. However, at Plane our methodology is "Tasks meet Methods", and we will try our best to do everything fitting in to this methodology.

We would love to see you try out Plane and share your valuable suggestions. Plane is new but its evolving quite fast.

Re: Plane: Open-Source Alternative to Jira

#234
post #90

Can it auto-delete issues untouched for the last 30 days? Idk if jira can, but this would be the single biggest productivity boost to any organization forced to use this sort of software.

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

Sounds like you've never worked on a project with hundreds or even thousands of backlogged issues that will never be worked on - it is the same as being deleted except is causes visual clutter.

Re: Plane: Open-Source Alternative to Jira

#235

Earlier quoted context omitted.

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…

You're assuming someone would fine the old bug from 2 years ago - it is easier to just create a new one.

Re: Plane: Open-Source Alternative to Jira

#236
post #230

Earlier quoted context omitted.

I've worked at a company that had Cancelled instead of Abandoned - so if you try and "cancel" a ticket you're given a model with two action buttons - Cancelled and Cancel: Cancelled cancels the ticket and Cancel cancels the modal.

You’ve hit my Jira pet peeve, kinda - accepting the default of naming the transition the exact same as the state it goes to. Transitions should be verbs. States should be adjectives. So your transition should have been called “Cancel” so your modal would have had 2 cancel buttons :D (Or yes, another term should have been picked!)

Yes Cancel and Cancel would have made no sense, and I think that should have told someone that Cancelled is an awful state name.

Re: Plane: Open-Source Alternative to Jira

#237
post #231
post #122

Earlier quoted context omitted.

jira-1369 is a 20 year old bug of email notifications not being put into a digest and instead flooding users. I for one feel like I grew up those people and we should share our wedding and other milestone photos and announcements on that chain.

Even though I’ve come to like Jira there are a few of these 15-20 year bugs that are just frustrating beyond belief. And a Jira PM will duck in there every 8 years or so to say they’re not considering it and then run away. Mine is how it’ll let you create infinite case variations of Labels, even though Labels are case-insensitive when querying, but it means the accidental variations people will make crap up the autoc…

Part of me feels like writing a new interface of what I need to Jira using their API to get things how they're needed while maintaining some meaningful compatibility.

Then I remind myself I'm not the only person to ever think that.

What amazes me is the number of times JIRA has landed at a clients while we are working with them (from us introducing them). It is excitedly rolled out to hundreds of employees on a project eam after they see what it can do with modifications for their workflow.

Every single deployment has eventually been shut down because Confluence can't digest updates every 5-10 minutes, nor can Jira.

A plugin isn't realistic in some cases, so some other ways was found around it.

Post reply on HN