The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Jira is the worst workflow management tool I've ever used. Why do Atlassian continue to layer anti-intuitive design upon poor performance and reliability?
Hi Joe Little,
if you experience problems with the workflow, please state the issue and the people here can hopefully help you.
If you want to propose some changes to the workflow, please help the Atlassian Development Teams by creating an issue:
I actually like the workflow management tool (the diagram) and am (or was, depending on whether or not I am in a next-gen board or not) able to create workflows, from basic to some based on Epics and roles in one workflow.What are the issues you are facing?
Why instead of the user picture now you are showing the name and surname first letters? Why I cannot create subtask anymore? Why all this popups? It was good the previous version, but the new one is anti intuitive, slow and unreliable.
I'm sure Joe is just expressing frustration rather then deciding to take the next year off to give a course in interface design to Jira employees, that probably won't read it anyway. I am also going to take this opportunity to express some frustration. I got here just by typing the question into google "why is jira so bad". I'm not an interface expert by any stretch, and maybe jira employees will be disappointed that there is no actionable criticism contained.
Still, what they should consider is that there are people who think their product sucks, and that a forum isn't the best way to probe for the actionable items to improve their product.
Here's one for you. I'm trying to look at the workload pie chart report. It does not seem to show accurate information. Why? I don't know. How could I search to find a solution to this? I don't know. What is the source of the data? I don't know. Is there even a help me understand this chart link? No.
Why can't I assign story points when I edit a task? Why can I only perform certain actions in certain views? What is the thought process behind the distinction? Honestly, even if there is one, I don't really care about it. I have a task in front of me, if I click on edit, I expect to be able to edit ever parameter of it. Like whoever made that decision should actually die on that hill. They are obviously taking a principled stand, and they should be punished for it.
Why does this website take more than 1 second to post a comment?
What is the exact issue with the work pie chart? Based on your comment, it could be anything, actually. I understand that this is part of the problem, the fact that it could be anything ;-).
I assume you're working with the classical board, based on the question about the pie chart. Depending on your configuration, you should be able to add an estimation on Tasks. Contact your Jira-admin and they could get this done for you. It's somewhat more complicated than the next-gen board, here you can easily add the estimation field to any issuetype you want.
There have been decisions made that don't really seem to make sense, but the fact that you want something in a certain way, doesn't mean everybody wants it in the same way. This is the everlasting struggle with software development and design. How are people using the software? What is the most common way?I believe this is why the next-gen boards provide so much freedom. It's the Atlassian type of Trello.
Estimations are added. Yet only 4 people on the team show up on the chart. And even those counts are not really accurate. Most frustrating is I have a zero. What is the difference between me and them? I don't know.
I'm used to flexibility. If its not a certain way, I should be able to make it a certain way. Rigid structures make for bad software products. So maybe that is part of the answer.
But your message is received. Jira is in fact bad. Even Atlassian, the company that makes Jira, offers better products.
no support - no proper reference - only paid courses in atlassian university. of course there are some free courses to get you going but you already know better than those free contents
Such a horrible product. Can't even upload images. They all break. Can't upload a file. Super slow. Is anyone working on this?
I couldn't agree more. I am constantly re-entering test detail steps, because every time I click the check mark to go to the next step it never adds the step I just finished, if I am lucky enough and it does, it is either missing what was entered in one or two of the columns. I completely dislike JIRA. So slow and frustrating. Entering test cases takes 3 times longer. I have to write my test cases outside of JIRA so that I am able to copy paste because the step details are not saved every time. My experience with JIRA has always been bad.
I feel all your pain since we have been forced to move to jira even though not one of the developers wanted this.
If they really want to see what is wrong with their product they could just google it.
Right now I am trying to figure out what a way to query what tickets I changed on a specific day, I am having no luck. Right now I am going one by one through what I can find. Why is the history telling me X days ago and not the date. Instead being able to quickly see what date it was I have to mouse over every one to see what date it was done on.
This is just one example of the extra time it takes to do anything on jira.
Management loves jira because it is visually pleasing.
Developers do not like jira because it is extra work.
I agree; at every turn there seems to be the strangest design choices. I have come to think of Jira and Confluence not as software products, but as sadistic performance art to see just how much abuse people will take before breaking.
My latest example (I come up with one every hour of using their products): I'm going through the byzantine process of allowing myself as an Admin to delete tickets, and I have four choices for granting delete to. None of them seem appropriate. Then I notice a little blue text - "show more." Now I have a dozen choices!
Why was it necessary to hide half of the choices from view using a random piece of text that isn't even graphically related to the choices? Why is every interaction with an Atlassian screen like an Easter egg hunt - with secret buttons and links scattered all over the screen?
I mean, the full dozen choices fit on the screen. Even if they didn't, the list could have been shown with a scroll bar. Instead, it's like Groucho Marx - "I've got choices, and if you don't like them, I've got others."
+1 To the general sentiment here -- the application is incredibly slow and extremely difficult to find anything with.Your designers must be using Jira as their workflow tool -- that would explain quite a bit. I feel like I'm trapped in a maze!
We've been using Confluence for a few months now and I have to say my engineers... love it. Once you accept its limitations and navigate its landmines and build a simplified work-flow that never expects more than "barely adequate," it's really handy.
If you just stop caring how your text looks, and accept that you have to post a screenshot of an Excel file to make it readable, and that every Jira story issue should be created from a specific screen by clicking on an obscure button (instead of using the big blue obvious button at the top of every screen), and a hundred other things, people really appreciate how anyone can just edit a page to make their contribution.
Mike perhaps you should put out a video or something. We were given Confluence it is pretty much empty. The developers looked at it and said NOPE.
You are better off installing mediawiki. Its free, has a ton of add-ons and is extremely usable.
I think we went with it because of JIRA interconnection, though we don't actually use that very much.
I've created a bare-bones starter kit for my company to use; it's six basic page templates, each of which is incredibly simple. We use it for project management and it's actually quite handy. As I said, the secret is to stop expecting what you want (or what is reasonable) and just use what they give you.
It is little more than a post-it note on the company refrigerator, really; but given that we are a small company and a small team, that's fine. It keeps track of everything in a place everyone can see and edit; and somehow manages to do that better than a shared Google doc (I still am not sure why).
So yes, mediawiki would probably serve my needs, now that I've reduced my expectations to almost nothing. But Confluence is actually quite convenient, as long as you don't expect very much. :)
We only use it because we are forced to. To many extra steps to do something simple. An example of this is moving an item. There is a second step that always says it is not required. why make the user click through it.
The UI is inconsistent, sometimes it opens in a tab, sometimes in a modal. Never sure which is going to happen.
Truthfully, the work flow is terrible.
There is nothing a developer likes more than adding extra work to do something very simple.
I've only ever used it because I wasn't given a choice.
Jira is and always has been a UX nightmare. Here's just one example (just happens to be my current example which drove me to be so frustrated as to find this page)
Create issue -> end up surprised it's listed on a specific "Board". The Co I work for has multiple boards. Why is this ticket....sorry issue.....in this board? Why is there no option to "move" it to another board? Why when you google this does some Jira "expert" say it's "nonsense" to "move" an issue between boards? Seems pretty obvious to me why I would want to move something especially since there is an actual menu option to "Move". But of course this "move" doesn't perform the move I want - just some absolutely garbage options such as move to a different project or different issue type.
Why is it "nonsense" to move to a different board? If boards are just filters then there should be something about this issue that assigns it to this board and not another board? What is that? Can't tell. No specific fields are any different from issues that exist in other boards.
It's this kind of stuff that drives people insane when using Jira. I honestly think Jira only still exists because any company that uses it would fall flat on its face if they had to try to migrate away from Jira. But I suspect that there are an extremely large number of unhappy Jira users. You hear about them _all_ the time. Not once has anyone ever said to me "Jira is the best tool" or "Jira is sooooo good".
Now there is JIRA WORK MANAGEMENT - another gutter product. They don't even know what they are up to
Part of the major issue with jira, is that you can have ONE user added to a group or switched to "trusted" etc., and if you delete the user or move them from that status too many times, even though no one exists on that status, the ACTIONS are counted - not the current user qty. with that status, and you have to "upgrade" to make it work right. Permissions mismatch their names and functions and too many nested menus exist that could be on a single pane.
Propagation of changes is a buggy joke, and the permissions "helper" is a misguiding tool to make you think you can troubleshoot Atlassians broken permissions management model. Deleted users magically still show up in groups and there is no way to do even the most simple things in bulk. EVERY tool worth its salt should have a way to check-box items and agents that can be done once (Maybe there should be an internal jira training to teach how loops and arrays work?)
Want to delete/move/change attributes for more than one user? Get ready for a night of doing it in multiple browser tabs individually to avoid having the page reload (since importing curated CSV data is also a joke).
Imagine if real life was built like this. If you put items in a box to move them all at once you'd get blocked because more than one item was in the box provided, and then a wrong message would pop up about your empty box being too full.
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...