Jira Is a Microcosm of What’s Broken in Software Development
81–90 of 182 posts
Re: Jira Is a Microcosm of What’s Broken in Software Development
#82Earlier quoted context omitted.
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…
Wow, that's as dumb as clauses get. 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.
Of course, that assumes such terms are enforceable. But, even if not, just having them in there is just so odious as to make one seek out other solutions.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#83You dont appreciate Jira till you no longer have Jira.
Then again I've worked on the project where the source of truth was a set of Excel documents shadowing 5 different ticket systems. Very briefly.
That said if you're lucky, JIRA can be set up to work relatively well. Especially if you keep it simple.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#84Re: Jira Is a Microcosm of What’s Broken in Software Development
#85"Bosses (managers) get stuff done through meetings – changing tasks every 60 minutes." -- I don't know what bosses you are or have worked with but incompetent leadership and poor software engineering acumen can't be solved with buying software subscriptions.
Why are you trying to make for the tool being bad when the blame lies with people? I am tired with hearing this bogus notion of friction between Bosses, PM, Engineers and somehow you can pay your way out of lack of alignment in an organization.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#86"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…
Yea spreadsheets were useful before and even more useful now. Agreed, they could be misused but what can't be misused ?
Re: Jira Is a Microcosm of What’s Broken in Software Development
#87OP sounds like someone who's unhappy working on big software projects. That's understandable. But once you're on a big project, you can't keep it all in your head. You can't make your own clever adjustments when problems arise without documenting everything and then taking it through channels. For what it's worth, sales people have the exact same complaint. They can get testy, too, about executives using software-ove…
Re: Jira Is a Microcosm of What’s Broken in Software Development
#88I briefly used Jira, but I couldn't handle the extreme slowness. You click something. Then you wait. And wait. And wait.
Cloud or Server? It seems a lot of companies’ reputation were broken by clients installing their software on 2GB/1.5GHz servers with HDD, and Cloud will help at least getting a consistent measurable experience of the same product for everyone.
Re: Jira Is a Microcosm of What’s Broken in Software Development
#89My struggles with Jira are more that the people who should be in charge of configuring it effectively and running it smoothly (team managers and PMs) often don't. I see a lot of stuff that's incredibly inconsistent and a lot of features that are used incorrectly (most prevalently using labels for EVERYTHING, usually using 4 different labels for the same purpose where say, a component or Epic would make more sense). E…
Re: Jira Is a Microcosm of What’s Broken in Software Development
#90I recognize that this is a marketing blog, but it blames Jira for what are really culture problems and/or bad management practices. This is an emblematic quote: Take subtasks, for example. The invention of Jira subtasks is an affront to dev teams. Clearly someone who has never spoken to an engineer on a dev team created it. It’s the least dev-friendly way possible to get insight into what’s happening with a Jira stor…