151–160 of 530 posts
JIRA is a bit like linux. It only really sings when you have a skilled admin to set it up and maintain it. I have used a whole bunch of ticket/project managing tools in a number of different orgs. By far the most useful is JIRA. taiga.io comes close, but lacks the admin interface and multi project overview that jira has. Trello is ok, but terrible for large teams, or large projects. Subtasking is a pain and there is…
To me, what sucks about JIRA (and would suck about any well-designed tool that replaces it) is not "feature x" but the entire JIRA mentality. All of it. It encourages micro-management. It encourages more and more process. It is the enemy of getting better at the DORA metrics, which requires streamlining process. tickets in JIRA are not the work itself, never was and never will be, it is a LARP of the work, but it get…
100% this. JIRA is bad because it encourages managers to use it to do stupid things, not because it’s inherently bad software.
To me, what sucks about JIRA (and would suck about any well-designed tool that replaces it) is not "feature x" but the entire JIRA mentality. All of it. It encourages micro-management. It encourages more and more process. It is the enemy of getting better at the DORA metrics, which requires streamlining process. tickets in JIRA are not the work itself, never was and never will be, it is a LARP of the work, but it get…
And I've also never worked anywhere that had a better option than JIRA.
To me, what sucks about JIRA (and would suck about any well-designed tool that replaces it) is not "feature x" but the entire JIRA mentality. All of it. It encourages micro-management. It encourages more and more process. It is the enemy of getting better at the DORA metrics, which requires streamlining process. tickets in JIRA are not the work itself, never was and never will be, it is a LARP of the work, but it get…
I 100% disagree. Fixing a bug or delivering a feature where you haven't documented the process, (how the criteria were decided, when it was tested and deployed) is as good a running a web site nobody visits. JIRA hate comes from the bottom up. Developers don't like having to have their work parceled out so specifically. But it's not for them. It's for managers and stakeholders who have to report progress and who are…
We are trying to unsuck Jira for users with an alternative UI, allowing them to manage Jira issues on a virtual whiteboard. [1]. [1] https://spartez-software.com/products/whiteboards-for-jira
Here's another product I found recently that allows users to draw out their project plan, and have it turned into management-friendly reports automatically:
No comment on whether or not this is actually good, since I have never tried it, but it presents a refreshing concept.
RT @HackerNewsOnion: California has ruled it illegal to conceal a company’s JIRA subscription for the purpose of attracting engineers. https://twitter.com/HackerNewsOnion/status/98160924222131814...
Do people really avoid companies based on their choice of administrative services?
I imagine you do as well! If you were looking for a job and they were programming in VB 6 and using CVS for version control I would imagine you (or almost everyone if not you) would say 'hmmm I'm not sure that's how I want to spend my day'.
I know I don't want to spend my precious hours on Earth trying to remember which markup syntax this particular input box uses in Jira today.
Earlier quoted context omitted.
I 100% disagree. Fixing a bug or delivering a feature where you haven't documented the process, (how the criteria were decided, when it was tested and deployed) is as good a running a web site nobody visits. JIRA hate comes from the bottom up. Developers don't like having to have their work parceled out so specifically. But it's not for them. It's for managers and stakeholders who have to report progress and who are…
I'm a developer and I can't remember anything so I love JIRA. I just grab a ticket and have everything I need to work on it.
Great article. As you are likely not native English, just as a tip you can actually simplify a lot of statements by removing the word ‘the’. As one example: > When the users need the features from Jira and request them to configure the plugins for many application scenarios, which contribute to the overall complexity of UIs. Becomes > When users need features from Jira they request plugins, which contributes to UI co…
Are both equally correct?
I am reading this comment thread and honestly I don't know that I agree. I think JIRA, like most tools, is as good or bad as you make it. I've been at numerous companies using JIRA that don't seem to have most of the issues referenced here. The only thing I've ever felt like JIRA really lacked in was in a good UX for embedding code snippets or other technical details into issue comments. Native support for Markdown i…
Jira Cloud has a new editor that is Markdownesque. Type as if you're using Markdown, and it will do the formatting you'd expect.
Holy hell, what a tragedy. I used to write markdown and have pandoc typeset a pdf in the company design. Now I have word.