You believe that Jira has "encoded" that culture in your company, not that your company has encoded it's crappy culture in your Jira implementation? Please see: https://en.wikipedia.org/wiki/Conway's_law
I don't have to imagine it. This is a textbook example of a Jira implementation failure not a Jira failure: "not having any idea how to use or configure it correctly to model the work being done."
There are myriad ways to misconfigure a cloud instance of Jira. You thought I was referring to the configuration of the actual web app I suppose. That's kind of a silly assumption but gives me a lot of insight into what you've said here...
A quote from a funny TV show still doesn't really make it a thing, does it?
If it's not, there probably is a way to do what you are trying to do that you just don't know about.
I work at a very large organization. The user lookups in Jira are lightning fast & the permissions are granular for a reason.
Can't help you with your billing problems but it kind of sounds like a "you" problem.
I have fully configured a Service Desk instance, yes.
It sounds like maybe you aren't actually using the release feature & or that maybe you don't know how to write JQL queries or maybe I don't know anything about the amazingly advanced way you are trying to use the features. "Hey doc, my arm hurts when I do this?" The doctor says "Then don't do it."
I could keep going too but it would be a waste of my time to try & have a reasonable discussion on something which you have prononuced your verdict: "Atlassian is a bunch of decent products drowning in scope creep, terrible cross-product integration, and a painfully slow development cycle that is focused way more on cosmetic features that fixes their trainwreck of a dumpster fire."
This is the most logical, sensible comment in the thread. Jira is the most flexible system for workflow management in existence. The fact that it is extensible is "a feature, not a bug."
I don't see really see anyone stating obvious truths about bad developers & software engineers (as shocking as it may be to read on HN that there are, in fact, objectively bad developers & software engineers with high-paying jobs at companies whose names you know.)
- they are more interested in making a new thing instead of fixing a broken thing they released
- they often can't remember how they built the last new thing
- that's because they aren't interested in building & documenting a fully working thing with test code from the start
- they aren't interested in data structures or architecture built to be easily maintained or in making scale part of their designs
- they despise being told to fix bugs because it is much easier to write code than it is to read it
I believe some organizations implement Jira thinking it is going to solve their cultural problems. This is magical thinking.
I am so tired of hearing about how terrible Jira is from developers.
It's usually the case that where Jira isn't working it has to do with the way it's configured (e.g., giving too many people access to set priority, setting too many priorities, setting too many components, using components in illogical ways, no one actively managing & grooming queues...)
To implement Jira successfully probably requires more work & effort to get it right than to not use it at all. The point of it is not to eliminate the work of issue tracking. It is to organize the workflow management of moving incredibly complex information from one person to the next. It's pretty great at this if you know how to use it.
I don't disagree with anything you said. I also understand that the "skip" you refer to probably is fun for people that don't have traditional musical experience. That's fine. However, anyone who thinks that typing start & stop into a terminal or text editor to trigger loops is MORE CREATIVE than playing a musical instrument is wrong.
> While playing off sheet music and focusing on dexterity exercises can be rewarding, they are not creative activities.
Of all the idiotic things written in the comments of HN (there are plenty...) this has to be, hands down, the most idiotic. There are literally an infinite number of possible expressions in terms of muscle movement & hand / eye coordination involved in an activity like playing the piano & this is BEFORE discussing the activity of using that infinite set of expressions to actually interpret music played from memory, by ear, or from a page. The fact that you think it's not a "creative activity" says more about your lack of creativity than anything else.