61–70 of 182 posts
Shots fired! It's true though. Using Jira is a struggle.
I started tolerating it after discovering it has keyboard shortcuts. Try pressing +? to see what's available in given context. + Make sure you have it bookmarked as search engine. Also makes it so much nicer when you can jump to specific ticket by using 'j FOO-123' from address bar. Or 'j whatever keywords' to do regular search.
I do remember working on projects before Jira. My first job out of college managed their software dev lifecycle with Bugzilla. I assure you, it was much worse.
Jira isn't bad, it isn't great, and I honestly don't waste much thought thinking about how bad it is.
I briefly used Jira, but I couldn't handle the extreme slowness. You click something. Then you wait. And wait. And wait.
Yeah. That part is bad and has somehow gotten worse. The animations don't help. They have a MacOS app now, which I've been meaning to try.
"Though I think of Jira more like a spreadsheet. Very useful once upon a time. Outdated now. Static. Manual." This statement is so blatantly wrong that it actually put me off even reading the rest. Spreadsheets are stronger than they've ever been and are never going away, let alone being "outdated." Sure there are products that claim to be "the next spreadsheet" but most of those actually serve a different purpose: n…
If you’re going to make judgements so easily you’re going to miss out on a lot of good ideas that people put out there.
"Though I think of Jira more like a spreadsheet. Very useful once upon a time. Outdated now. Static. Manual." This statement is so blatantly wrong that it actually put me off even reading the rest. Spreadsheets are stronger than they've ever been and are never going away, let alone being "outdated." Sure there are products that claim to be "the next spreadsheet" but most of those actually serve a different purpose: n…
Or rather, the platform for "this is the only b*d tool IT have allowed me to run, and no, I don't have a spare year for them to scope out what could be bodged by a couple of VBA scripts, and doing so would very obviously make my job better. So, for good or evil, it's going to be bodged with a couple of VBA scripts."
I feel like there's a lesson there, though I could be wrong. (Also not sure if that counts as "no-code")
Oh, and seconding the general consensus that websites that flash irrelevant notifications at me are pretty much an instant, hard "no".
I spend hours per day in Jira. Half as a PM, and the other half as an IC. I've never used Jira Classic, so can't comment there. But Jira Next Gen projects have been great to work with. So much functionality and bloat is stripped out of Next Gen, sometimes too much was removed I think. I hear people hating on Jira very often, but at least the way our company uses it, it's great. The only thing I'd really want to chang…
> performance By Atlassian’s ToS, you are not allowed to « comment on the performance of the products ». I know no-one thinks this would be enforced here, but I just want to highlight that it doesn’t help a company to improve if they know they can just lawyer-up a problem away and avoid benchmarks and being compared on that topic.
I totally understand that benchmarking is hard, but using legal means to silence anyone from talking about aspects of your product is just downright scummy.
Earlier quoted context omitted.
> performance By Atlassian’s ToS, you are not allowed to « comment on the performance of the products ». I know no-one thinks this would be enforced here, but I just want to highlight that it doesn’t help a company to improve if they know they can just lawyer-up a problem away and avoid benchmarks and being compared on that topic.
This is from Atlassian's ToS (d) incorporate any Cloud Products into a product or service you provide to a third party; does this mean that I can't integrate JIRA into a ticket tracking workflow that I build for my product with IFTTT that creates a new ticket when someone sends an email to a support alias? (e) interfere with or otherwise circumvent mechanisms in the Cloud Products intended to limit your use; (f) reve…
I'll try to get the legal team on it. It's a landmine as even a casual discussion of performance voids the license. Any discussion of outage may or may not involve this point.
It is a devops prevention clause.
Earlier quoted context omitted.
If you’re going to make judgements so easily you’re going to miss out on a lot of good ideas that people put out there.
I would say 90% of tech ideas that area floated out there are awful and I'm being pretty generous with that number.
Anecdotally, the most frustrating company I ever worked for had obsessive Jira practices, but there was so much wrong with that company I could write a book about it.