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?
The issue type name is not visible in the new view. Only the icon.
Hi @Ian Bucad Issue type is always visible on the view screen, even you add it on view screen or not.
thanks
I'm not seeing it unless I hover over the icon.
For reference, this is the old view:
And below is the new jira issue view where I have to hover on that itty bitty icon
We have the same icons for several issue types - any suggestions how to know the issue type?
Change the icons. :-)
Also, if you hover over the icon, it will tell you the issue type.
Sure :-) We need to get more and more creative in compensating missing usability from Atlassian side ;-) Unfortunately we have users who's primary work is not understanding JIRA, but real work :-(
The icons I already changed, but the feedback was not so positive ....
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.
Same here. Trying to get marketing, training and a few other groups involved to product rollout plans and get out of emails and spreadsheets. And this situation has been consistent feedback that they don't know what issue type they are on.
I've created a Suggestion over at Atlassian Support. Feel free to vote for it by clicking "More" > "Add vote"
https://jira.atlassian.com/browse/JSWCLOUD-21528
Thanks for doing that - voted!
This already existed - I linked to it earlier in this thread. By creating a second one, you're simply diluting the perceived interest in restoring this visibility.
This new Jira view is a hot mess. What a horrible design decision for one of Jira's most important fields. Please restore text visibility to Issue Type and trash the icon mouseover baloney.
Clarification on Hovering to see Item Type
Note: the initial request to add this is here: https://jira.atlassian.com/browse/JRACLOUD-73516
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.
Just in case anyone else is looking for this, although you can't see the text for the "Issue type", you can include the "Request type", which I find is often the more "user friendly" name anyway:
I have just gone through the same process of trying to work out how to display the Issue Type (Name) on the Issue screen, rather than just an Icon.
The problem is not with showing the icon, it's the fact that the JIRA software specifically denies allowing you to display the Issue Type as a regular field. Someone has actively gone to the trouble of preventing you showing that field in a conventional manner.
I will vote for this to be fixed -- since we have moved to the cloud version of JIRA we are finding numerous backwards steps, although we really had no choice in the matter given the on-premise version is being discontinued.
https://jira.atlassian.com/browse/JRACLOUD-73516
Another workaround, which we should not need, is to toss a field on each issue and run a small automation in the background to update the field based on issue type. Add that new issue type field to your view and tada!
There is likely a plugin available for that.
I hope you recognize the narcissism.
When will give have decent CX... it sucks
It looks like you're new here. Sign in or register to get started.
