+1

Need this badly. Not being able to see what is the issue is inconvenient. You can't just hover over the issue everytime you want to see which type of request it was. Please fix. 

Agree, this is critical functionality IMO so that users don't have to hover over to see a basic description, plus the icons all look the same

This would be really helpful and shouldn't have to be a paid for work around. 

Thank you so much Joseph & Gordon! Works perfect!

Hi all - thanks for the comments. What do users like me to that do not have the ScriptRunner (apart from getting it  ) I think this is something that should be configurable. Thank you

Works also with app Jira Misc Custom Fields (JMCF).

Create Custom Field of type 'Calculated (scripted) Text/Html Field (JMCF app)'
Groovy Formula: issue.getIssueType().getName()

Fantastic Joseph! Thank you so much for sharing this! Note to other Scriptrunner novices like myself - you create the custom field as Joseph describes in Jira Issues admin but you add the short script to it in manage apps/ Scriptrunner admin/Fields

This works a charm! Many thanks for sharing.

If you have Scriptrunner you can create a Scripted Custom field and use this one liner:

issue.getIssueType().getName()

Don't bother adding the custom field to a screen, just leave it globally available to all projects, and you can now add Issue Type, Issue Type Name, or both to Issue Navigator Queues and Dashboards.

Hope this is helpful.

I second everything that was written before me. Managers need the value of the "Issue Type" not a pretty icon it represents. Please get it done.

+1

This is a genuine PITA. Also, when using the Jira Issues macro in Confluence, the Type column comes back as icons, not text like 'Story', 'Epic', 'Risk' etc. An icon is useless for other macros to use for filtering or exporting.

Given that in JQL we can search for the type of issue by its text name, it seems absurd to only be able to get back a non-text result. Add a new value to return, such as issueTypeAsText so that we can choose which to return.... an icon or the text.

Managers want to use search filters for tabular reports. Putting icons in them is useless. Even when I subscribe to a filter, the email contains the icons.

As a result of this I have to explain to my bosses that this is yet another tiny little niggling Jira design decision that breaks reasonable use cases.

No. Please fix this.

For now I will try and work around this unfortunate decision by using a 3rd party plugin to copy the Issue Type into a text field and reporting on that. And then, if a ticket's issue type ever gets changed, I get to handle that use case myself, too. I get paid by the hour, so thanks I guess? But really, I have enough to do without spending time adding basic reporting functionality in to Jira.

Still needed

There are so many basic functionality gaps in this product its not funny and people have been complaining/asking for about the same the same things for years. 

These issues wont get the votes as people have given up asking for things to be fixed.

Do any of these things ever get actioned?  

This is really basic stuff, asked for years ago.  It's ridiculous that one of the most basic and important issue fields isn't readily visible in results, for no apparent reason at all.

It's not assigned to anyone and until it gets more votes/comments nobody in the team will even look at it?

This feature is especially helpful for systems that have many issue types, as pointed out above. 

 This would be super helpful!! 

please add this!

It's inconvenience to show only icon of issue type when users are searching for issues.

It would be much helpful to add this feature. Thanks.

Please add this feature.

With multiple in-built and custom fields with the same icons, it's hard to categorize them when the issue lists are exported.

I would like the ability to toggle between the issue type icon and name.  Displaying the icon is a good idea if you have very few issue types, but it becomes very unpractical when there are several issue types in one instance.  As noted above, the system stores and retrieves this information anyway, it should not require a major developmental change to implement a different display.  This could be added to the Look and Feel Formatting section. 

(Slightly related: it would be nice to have the date/time display - time stamp rather than relational text - option here too instead of manipulating a config file on the backend of the system.)

Seems like the idea of using an icon is to save screen space, but when the icons are mostly the same for 100 issue types, then that doesn't work. I see the KB suggests a change to a source vm template. I think I'd define a scripted field with ScriptRunner and display that in the search results instead of the standard Type field. The script could truncate the issue type name to something unique but not too long

So many of the icons look alike they serve no purpose to the user.  Trying to hover over takes more time to accomplish then it should to get the work done.  I guess, I could select some other kind of avatar, but the actual words would serve the purpose. 

The issue type description is one of the most important fields to the agent. Displaying it only as a hover is ridiculous.

The agents want to see a view of issues including their type.

I have to say it's confusing that this information isn't readily available to display, since it's obviously being retrieved - hovering over the icon for the issue type yields a pop up with the name.  So it's being inserted into the HTML for the page which means that there's some mechanism that can retrieve it.