-
Suggestion
-
Resolution: Won't Fix
-
530
-
71
-
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future, but we did want to share two workarounds for this ticket that might be helpful:
Workaround 1: Hover Over the Icon
In the New Issue View, users can hover over the Issue Type icon to reveal a tooltip displaying the Issue Type name. This ensures that users who need clarification on the Issue Type can easily obtain this information without adding clutter to the interface.
Workaround 2: Use an Automation Rule to Populate a Custom Field
For users who prefer the Issue Type name to be explicitly displayed, a custom field can be configured through Jira's Automation functionality. The process is as follows:
- Create a Custom Field:
-
- Go to Settings > Issues > Custom Fields.
- Create a new text field, such as "Issue Type Name."
- Set Up an Automation Rule:
-
- Go to Project Settings > Automation and create a new rule.
- Use the trigger "Issue Created".
- Add an action "Edit Issue Fields".
- Set the "Issue Type Name" field to populate dynamically based on the Issue Type (e.g., using {}{{issue.issueType.name{}}}).
- Apply as a Single-Project Rule:
-
- To avoid exceeding the monthly rule execution limits, configure the rule to apply only within a single project. This ensures unlimited executions and localized management.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Best,
Ahmud
Product Manager- Jira Cloud
On the Old Issue View, Jira displays the Issue Type icon and the Issue Type name beside the Issue Key.
On the New Issue View, Jira displays only the icon for the Issue Type which can make it difficult to identify if which Issue Type the issue was created.
Suggestion
Add the Issue type name on the New Issue View instead of rover the mouse over the icon.
Workaround
Workaround 1
Currently, you can hover over the icon of the issue type, which will show a text with the issue type's name:
Workaround 2
It's possible to create a text custom field and fill this through an Automation rule whenever a new issue is created. The rule structure would be the following:
It's a good approach is to create single-project rules to avoid using monthly rule execution limit. Automation rules execution is unlimited for single-project scope rules.
- is duplicated by
-
- Closed
- is related to
-
JRACLOUD-76449 Issue type name is not displayed when you do not have permission to edit issue in the new view
-
- Closed
-
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
[JRACLOUD-73516] Display the Issue Type name on New Issue View
I can't believe this is even an issue. Why on earth would you ever NOT BE ABLE TO DISPLAY ANY FIELD, ESPECIALLY ISSUE TYPE?
I'm evaluating Jira for backlog management. 2 days left on the trial. I've spent HOURS trying to figure out what I was doing wrong to not see ISSUE TYPE. I'm stunned this just isn't possible. With this, I will likely NOT proceed with a purchase. Sad, because everything else is fine.
Classic case of Why fix what works. Why would you remove something that was working well (from what I can see here)?
OK, SO I CAN HOVER OVER THE TINY GREY BOX (THE ISSUE ICON BECAUSE I HAVE NO PICTURE SET), BUT WHO IN THE WORLD WOULD KNOW THAT? WHO WANTS TO DO THAT JUST TO SEE WHAT THE ASSIGNEE IS BEING ASKED TO DO? THIS IS IDIOTIC!!
Please fix this. It feels like moving backwards when users have to hover over an icon to see what Issue Type it is. Thanks!
Please give us the option to either display the Issue Type field itself, the associated icon, or both.
Workaround 2 is not really an option with the limited amount of automations you can run. We went through automations in a couple of days having them trigger on type change and issue creation.
We've started just getting used to workaround 1.
Totally agree with all the other voices here. This feature is very useful! Please, put it back, if it possible! Thank you!
Totally agree with all the other voices here. As a user / administrator I must have the option to show the issue type name. Also think with regards to accessibility: an icon isn't a text replacement.
We newly migrated to cloud. Long story short, someone needed to see/change the issue type and came to me. Took me 1/2 hour to find that this icon business is the way. What? Please add a text field back, or the option to display a text field.
The present functionality is not intuitive.
The "Apply as a Single-Project Rule" note in the workaround is based on the old way of calculating rule usage. The new way counts any rule (even within a single project) that does an action towards your limit (with a couple of exceptions but a rule that sets a value in a custom field does not fall into those exceptions).
In Screen Layout they still list the "Issue Type" field, it just doesn't work when added, seems like the best option to let it count like a real field again and let users who want "clutter" (or efficient display of information in a non-ambiguous manner...) add it to their screen / layout like we used to be able to.