Re:JIRA is an antipattern
by augbog on Sunday December 09, 2018 @02:59PM
(#18642923)
I agree with a lot of these things -- although I will say it took us a lot of time and the right people to help SET UP JIRA to be able to work with our process.
[ Parent
| on HN ]
This. Setting up Jira invariably meant searching internet for me. I have seldom worked with less intuitive UI (Outlook comes to mind, but it is a much smaller app). In light of this article - is it because noone had a clear vision of the app and they all just implemented tickets?
Re:JIRA is an antipattern
by angry_octet on Sunday December 09, 2018 @05:05PM
(#18643575)
Sounds like they had no process to begin with, found a ticket tracking tool, made fulfilling tickets their process, and now blame the tool.
That's kind of funny to think about. I'm pretty sure most of JIRA's configuration faults are from over-zealously fulfilling every wish their customers in the early-to-mid level stages had. I'm always confused by the "workflow screen" section and why it was ever done that way.