Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-60945

Show Issue Type Name instead of Icon in Issue Navigator

XMLWordPrintable

    • 8
    • 4
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Issue Summary

      When a user performs a search and the result includes a lot of issue types, the user is presented with the icons for these issue types instead of the name of the issue type.

      In essence, making it difficult to easily discern which issue type each issue is if they have used same images as icons.

      Feature

      Can an option be added that lets the JIRA admin toggle between showing the issue type name or it's icon for their instance.

      Existing Behavior

      JIRA would only show the feature name if no icon is associated with it and there's no way to toggle between the two.

      Known KB that Achieves feature partly:

            [JRASERVER-60945] Show Issue Type Name instead of Icon in Issue Navigator

            Sabbir Quarishi added a comment -

            +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. 

            Sabbir Quarishi added a comment - +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. 

            Jeremy Scheppers added a comment -

            +1 : it is a pain as it limits readability in lists used for revieuw/audit purposes within teams.

             

            Jeremy Scheppers added a comment - +1 : it is a pain as it limits readability in lists used for revieuw/audit purposes within teams.  

            Kevin Jackey added a comment -

            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

            Kevin Jackey added a comment - 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

            Aidan added a comment -

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

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

            Manfred added a comment -

            Thank you so much Joseph & Gordon! Works perfect!

            Manfred added a comment - Thank you so much Joseph & Gordon! Works perfect!

            Yatish Madhav added a comment -

            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

            Yatish Madhav added a comment - 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

            Stefan Brunner added a comment -

            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()

            Stefan Brunner added a comment - 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()

            Gordon Rutherford added a comment -

            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

            Gordon Rutherford added a comment - 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

            Glenn Provoost added a comment -

            This works a charm! Many thanks for sharing.

            Glenn Provoost added a comment - This works a charm! Many thanks for sharing.

            Jordan Loverock added a comment -

            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.

            Jordan Loverock added a comment - 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.

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              168 Vote for this issue
              Watchers:
              76 Start watching this issue

                Created:
                Updated: