201–210 of 238 posts
I just want a simple customisable ghant chart
https://github.com/makeplane/plane/tree/develop/apps/app/com...
Earlier quoted context omitted.
> Your first bullet list of features doesn't really make it sound all that different. It's... free? Isn't that a pretty big difference? https://www.atlassian.com/software/jira/pricing
Not really. Jira licensing costs are on the order of about 10 minutes of employee time per month. So, if it is even slightly worse it's a financial disaster. (Of course, Jira itself is hell, but then what is a likely-buggy and feature incomplete version of hell?) Plus, even if the software itself is free, you still have to host it somewhere.
You end up with many many hours of employee time per month spent on licenses for SaaS products that you never own, can't control, and often can't extract your data from if you want to bail.
So yeah, as a middle manager trying to cut costs, any free alternative to a SaaS product sounds good to me. It beats dribbling out licenses piecemeal and living without core functionalities (looking at you monday.com) to stay within the lowest payment tier where I can see that 10 minutes-employee-time per month.
I admit that paints products like Jira in a bad light and ignores all the upsides (no hosting issues, upgrades are automatic, etc.).
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…
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…
The biggest issue, in my experience, has always been its performance. Perhaps I have only worked in organisations that have completely misconfigured their Jira instances or the servers are underpowered, but even with the Atlassian Cloud, I am used to waiting 10 seconds to move a ticket from one column to another. Or add a ticket to the backlog, click the backlog, ticket isn't there yet, refresh the backlog, it's ther…
We went with Asana. I miss the ability to create epics and do proper sprints, but at least the things load when you click on them.
Conversations about why it's bad for developers or product managers or attempts to show them how to get the same value in another way often fall on deaf ears (or don't happen at all) because it's the only way that they know how to work.
One of the key indicators that this is happening is when people start saying things like "this can't do Agile because it doesn't have PET_FEATURE"
Jira isn't just software, it's a way of working that's become the de facto standard, and it's hard to get out of that box for a lot of people.
Earlier quoted context omitted.
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 wit…
>it does not explain, why seemingly every single Atlassian product including Jira sucks at parsing Markdown or supporting Markdown well. Australian here, I can provide some clarity on that. Australians in general are fairly lazy; we like to do the bare minimum necessary to get the job done so we can knock off work and grab a beer at 4pm. Atlassian is an Australian company, and has generally inherited such an approach…
Please, kill Jira and Confluence. I hate Atlassian tools so much. The user interfaces are sluggish no matter the hardware you're using... it's a shame it became almost a standard in our industry.
Indeed it is a shame that they still a thing.
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 wit…
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…
The biggest issue, in my experience, has always been its performance. Perhaps I have only worked in organisations that have completely misconfigured their Jira instances or the servers are underpowered, but even with the Atlassian Cloud, I am used to waiting 10 seconds to move a ticket from one column to another. Or add a ticket to the backlog, click the backlog, ticket isn't there yet, refresh the backlog, it's ther…
Before the new UI came around in ~2017 it performed pretty well and if you were judicious with customization it was easy to use. Everyone knows Jira so it was easy to get new people started with it. Then the redesign came out.
I opted in for a bit when it was in Alpha but bailed because I had trouble getting my job done in trivial ways. I'm normally pretty accepting and friendly to new UIs, even if its rough at first. I generally accept that I won't like most at first because it disrupts my workflow in the short term. Usually once I relearn the project its for the best. Not with this one. It's just so damn slow. It's terrible.
I'm not in a position where I pick our project management/documentation tooling anymore, but if I was I don't know what I'd pick. It used to be that I wouldn't think twice, now Jira isn't seriously in the running anymore. I think notion has beaten out confluence even if I'm still not in love with it.
Earlier quoted context omitted.
I used JIRA at, I think, every single company I've worked at and I never really liked it much... But the company where I work at right now has a really well set-up JIRA board where most things that I need to do are easy to so and there are clearly defined workflows. Compared to the morasses of legacy code I have to wrestle with, I find JIRA now to be one of the least troubling aspects of my work day. I'm sure it was…
> I'm sure it was super painful for the people who had to actually set up the current flows, but I guess that once you customise JIRA to your needs, it can work really well. The issue probably is that many companies don't want to bother setting up good, streamlined processes, or just don't know how. It’s actually not as bad as you’d think to set up. The reason Jira is so universally hated is because everyone uses it…
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.