I am trying to have the Issue Type displayed while in New Jira issue view.
I have added the "Issue Type" to the Configure Screen's Field tab but I still can't see in under the Project's issue layout page.
What am I missing?
Not sure that I would classify it as missing usability since you have the option to change a standard icon.
But regardless, what exactly was the feedback that they didn't like about the different icons for each issue type? We have more than 100 issue types and lots of creativity with the icons so it is pretty clear what the issue type is.
Can you provide more feedback?
If usability means you have to learn the meaning of icons, fine. I would not share this view. If you force me as manager (not the ones permanently working with Jira) to look into a tool like Jira and on top expect me to understand hundreds of different icons - sorry I would refuse to use Jira and require proper reports (back to old school).
So the feedback was simple and clear: "I/We do not want to remember icons, I/We want to read the type, so I know in which level of hierarchy the issue is and what it means."
Hoovering over the icon was unfortunately also not an argument.
We can arrange almost every single field in the screens, but we are not allowed to display the issue type. This remembers me of a paradox situation at a clients new office, where the architect and consequently the purchasing department (!!) refused to organise pinboards with the argument, that we have meeting rooms with whiteboards, and this is sufficient for the new working environment.
I don't want to provide more feedback - for me (or at least for the management I try to convince to look into Jira) it's missing usability.
Just to chime in, I agree that this is an absolutely horrible design decision. I'm seeing first hand how it's incredibly hostile to new users especially, and those are the ones most likely to jump ship if they're not getting the experience they expect (and, frankly, deserve).
Having to remember a bunch of obscure little icons is ridiculous. Was anyone really complaining about having the text of the issue type name present before? This seems like an answer for a question no one was asking.
For anyone else who happens across this, there is a "suggestion" for returning the text of the issue type to the view screen. It looks like it hasn't gotten much attention yet. Vote! :-)
Yes, I'm aware. But that's not obvious to a new user, so each one needs to be told about that. Also, it's an incredibly frustrating experience to have to repeatedly do that while trying to get acclimated to a new application. I've watched this play out in real time, and I can feel and understand their aggravation.
I find this whole thread so amusing.
Atlassian removes functionality (for instance displaying something basic like what issue type an issue is) and then when people complain, instead of admitting functionality is removed the complainer is gas-lit! "Oh, we added ICON FUNCTIONALITY! Why are you complaining!".
Oh my god it is so rich.
So I am curious who was gas-lit and which comment was made about not complaining? Also, which comment said functionality was not removed?
It's a new view, so you can adapt or you can complain. I simply choose to adapt in this case. I was simply pointing out that you can still see the Issue Type by hovering because it seemed to me to be implied by comments that the user do no longer see the issue type name period. That's simply not the case.
I fail to see any complaints attacking the complainers, but I am certainly open to light being shed about that.
This is the best.
Look, Atlassian took a product that everyone is stuck with due to institutional lock-in. Then they decided to totally revamp it without asking admins or other stakeholders whether they even WANTED a revamp. Then they decided to do the bizarre changes by rolling it out across different users at different times to use them as guinea pigs. And without acknowledging that they were removing a ton of functionality (Tabs, etc). They also forced it to be opt-out on a user-level purposely keeping admins from shutting the horrible thing off.
Then when people complain the complainers need to prove their complaints are valid and even prove that there are complainers!
You are too much man. I am not saying you are to blame. Or that you are doing anything wrong. I am just saying your response to ANYONE complaining about this new view fiasco should be "Well sorry you got the carpet yanked out from underneath you, being an admin is HARD and even harder when everyone around you is stressed out doing their normal job, and now you have to learn bizarre work-arounds that are only temporary anyway, because atlassian will FORCE you to use their junky new view whether you like it or not on March 31st, and even worse yet, many of the work-arounds require training the END USER on how to use the gee-whiz-look-at-my-slick-GUI-changes-that-DO-NOT-HELP-ANYONE-DO-ANYTHING-BETTER-THAN-THEY-USED TO... so yeah, sorry about all that, but now having admitted that, how can I help you out?... oh yeah, you can hover over that icon to find out something that you used to be able to see at a glance and you can train your WHOLE COMPANY TO DO THE SAME HOVERING B.S. - I can see how that would be super annoying... AND THAT IS JUST ONE SMALL CHANGE THAT IS ANNOYING, there are so many more you will have to overcome, but that isn't the price of progress that is the price of a company that doesn't care about its end users trying to make their product look cool on mobile phones and making the poor choice of forcing every bad design decision that entails become YOUR PROBLEM as an admin, and yeah that is not something anyone should have to do but here we are..."
The whole thing is hilarious. If I didn't have vendor-lock-in I would get my organization the hell outta here. But here we are.
My overarching point here is:
A) People have a right to complain and there is a lot to complain about!
B) Don't act like explaining how to do a workaround is anything other than an embarrassment for anyone involved including yourself. FACT: There was a field that told users what type of JIRA issue they were on. FACT: That field is now gone. FACT: That is ridiculous but whatever!
Please don't take this personally. It isn't an attack on you. I am just admonishing you to acknowledge that the new issue view causes problems. LOTS OF THEM. And then go from there. I am sure you are super nice and helpful and, no sarcasm intended, you are making the world a better place by helping everyone out. So sorry if I sound like a jerk. But oh my, I just can't even. This has been a fun ride. Thanks Atlassian! I can't wait until March 31st!
Look, I feel your pain as much as you do. I dislike the new view as well. In fact, I will be using it up until the day they take it way from me.
My point is just that you know it's coming and that's not going to change. So until there are updates there are ways to use the tool as it is. Doesn't mean that we like it.
And nobody is saying you can't complain. I have done plenty of complaining myself. This just isn't the place for it in my opinion. Atlassian is rarely looking at these posts. Especially ones that are months old. So I view this arena in the Community as a way to help people get stuff done with what we have.
Feel free to vent away, but you aren't really reaching anyone that can do anything about it here - sarcasm or not. :-)
"My point is just that you know it's coming and that's not going to change." - that is what people said about a Trump presidency in 2024. The new issue view is so garbage that I bet they back down once March 31st arrives, or a few weeks or months later.
Also, if you are right and they don't keep their toe in their own community forum during the biggest major overhaul of their software ever then they are one sad sack pathetic company doomed to implode much sooner than we all think despite the pain of vendor lock-in that we all think is going to keep us chained to them. JIRA is NOT FORTRAN. It can go bye-bye in the span of a year if they piss all their customers off simultaneously. Which is probably why they did the unethical rolling user-level optout switchover over the COURSE OF AN ENTIRE YEAR. They were hoping to sneak it all in and then flip a switch once everyone got used to the cold water thrown on them, while spreading the pain out so people never complained en masse and instead in trickles as each was jolted into the world of the great "new issue view".
Do you know how much work it would be for me to yank my organization from JIRA? A LOT. And yet, yesterday I began researching how to do it. That is how badly they botched it. And I am NOT the kind of guy who creates extra work for myself.
So I must disagree, they probably DO read an occasional angry screed sitting around here, and if I am lucky I can win that cranky old dude lottery. Hence my venting on top of your honest attempt to help others out. I am not in the habit normally of getting drunk and knocking over the Girl Scout Cookie Table at the local supermarket. But good god I cannot stop myself.
In this post-covid-world where everyone is AT HOME ON THEIR LAPTOP - do they REALLY need to go through with their ridiculous overhaul designed to make JIRA look good on mobile phones? I hope to god not. WAKE UP ATLASSIAN. YOU ARE MORE OUT OF TOUCH THAN A BUNCH OF NUTTY QANON FOOLS.
I've just lost a day of work looking for issue type on the screen. Found the dot-size icon only thanks to this post.
I reviewed all the settings, screens, fields and so on to no avail.
As I am setting the project for people who will work on multiple issue types, the issue type is the most important information regarding the issue.
As the people who will work on this are neither Jira experienced, nor they will use Jira full time, the icons will be meaningless to them, at least during critical period of adapting Jira.
So what's the user instruction? "Once you open the issue, locate a dot-sized icon towards the top of the screen, located along some other meaningless icons, hover the mouse over there, read and remember the text, which will disappear, then you can start working on the issue." Any better options?
Not sure this design will help with the successful application of the tool.
Clarification on Hovering to see Item Type
Agree with the comments. Creating icons that are all different is challenging for accessibility and readability. Chores and Tasks - you might say why would these be different types? Well, they can have different workflows and fields because the persona is different. However, how we would want to convey in a UI and at glance, is using the same icon.
It's not intuitive to have to hover, especially when you have it in your configuration to show on your screens.
Why take on the battle of not providing customers the ability to have it on their view screens or not? Jira provides alot of configurability for that reason and to take that away on certain fields, creating these 'exceptions' is the frustration.