5 ms·
I've developed against JIRA and used JIRA pretty heavily at several companies now. JIRA is a really nice product, but one's experience with it heavily depends o
by nunez 9y ago
I've developed against JIRA and used JIRA pretty heavily at several companies now. JIRA is a really nice product, but one's experience with it heavily depends on who "owns" it.
- rando444 9y agoThis has been exactly my experience as well.
- walterbell 9y agoIt helps if JIRA users (i.e. developers) help to define the workflow.
- megy 9y agoOh yes, not allowing others to go back and edit tickets is a huge one for us.
- wwalser 9y agoFinally, someone makes _the_ point in a thread about JIRA. JIRA's most powerful feature is that it affords for mapping businesses processes onto software. This is incredibly compelling to enterprise customers. Software that enforces workflows, procedures and requirements can be an incredible lever and JIRA's price point makes build vs buy decisions an absolute no-brainer. The down side for the true end-users, those who actually use the software day-to-day, is that most business processes are awful. If your experience is the hellish existence that I see strolled about on threads where JIRA comes up, I can say with near absolute confidence that it's because of one of three things: * Your admin(s) set it up once and hasn't bothered to iterate on those workflows. * The business mapped their autonomy stripping processes onto JIRA intentionally. I'd guess that most of your work experience is similar. Process stifled nonsense. * You're on an instance that is serving too many people with too few resources. Shard your instances folks, the money for extra licenses is wildly cheaper than the human time you're wasting waiting for stuff to load.
- brazzledazzle 9y agoExactly. Conway’s Law doesn’t just apply to software you produce but also how you configure things like JIRA. If JIRA sucks chances are you’re probably looking at a reflection of your organization’s dysfunction.
- seanjregan 9y agoLearning from Conway's law.
- sytse 9y agoThat is very well put. I quoted this in our product handbook https://gitlab.com/gitlab-com/www-gitlab-com/commit/be35fdc440968a11d35c11b6bfa1190559dfec91 https://gitlab.com/gitlab-com/www-gitlab-com/commit/be35fdc4... Thanks!
- marktangotango 9y agoWhat have you developed for jira? Plugins? What type of functionality? Do you have any advice for someone desiring to develop a plugin and sell a jira plugin?
- nunez 9y agoLots of automation. Creating/managing issues and tying them back into other biz processes, i.e. significantly worse tools (think: ServiceNow). Easier tools for managing issues from the command line. That sort of thing.
- MichaelMoser123 9y agoWith bugzilla everyone can understand what tasks exist. With jira you need a manager for what. Control of the information flow is the basics of geek politics.
- draw_down 9y agoI hear this take a lot, but it really fails at some basic usability stuff. For example, the way it does code blocks breaks all the time, especially if the content has curly braces. As, you know, many many languages do. I think we can just admit to ourselves that JIRA is bad. It’s ok to say it.