With JIRA and Confluence, there is never just one JIRA or Confluence. It really comes down to the configuration. And there are hundreds, if not thousands, of different configuration options that could be built into your particular implementation which may make it sing, or make it like a bad CAFO.
I’ve been part of a team doing JIRA and Confluence configuration. We saw on,y the tiniest bit about the configuration process required to make it work, and we slammed that hood right back down and decided we were never going to look under there again. Well, not ourselves. But we did hire a JIRA and Confluence expert to come in and help us make it as optimized as we could get.
I’ve also been a customer of bad JIRA and Confluence configurations. And when they’re bad, they can be really bad. But, as a customer, you don’t have any control over those system configuration options.
It’s like saying that a hammer is bad. Well, which hammer did you use? There are dozens or hundreds of different types of hammers out there. How did you use this hammer? What did you use this hammer on? Where did you use this hammer? Were you trained in how to use it properly? Did you actually use it properly, or were you using it in a way that was not consistent with its design?
There is no one JIRA or Confluence.
