How to Set "Epic" as Default Issue Type in List/Board View?
Asked by Muhanned Shahada:

Hello Jira Work Management Community,

I've encountered a challenge in my Jira Work Management setup that I hope to get some guidance on. When I attempt to add a new issue from either the list view or board view in my project, the issue type defaults to "User Story." For my workflow, it would be significantly more efficient if the default issue type could be set to "Epic." Because i keep having human errors from the team to create stories issue type instead of epic because they were in rush.

Has anyone successfully configured their Jira to default to "Epic" (or any other issue type) when creating new issues from these views? If so, I would greatly appreciate it if you could share the steps to achieve this.

![Captura de pantalla 2024-02-26 a las 15.32.40.png](/t5/image/serverpage/image-id/308668i9C9F3F8D52A3E7FD/image-size/large?v=v2&px=999 "Captura de pantalla 2024-02-26 a las 15.32.40.png")


Answers:
author: Marie H
body: We are experiencing this same issue, have done the same troubleshooting, and have submitted a ticket.


author: Nikola Perisic
body: Hello [@Muhanned Shahada](/t5/user/viewprofilepage/user-id/5408570)

Sadly, there isn't a way of setting a default issue type to be Epic since it doesn't have an issue type scheme rather, adding new issue types which doesn't have an option to choose a default issue type.

This would be possible in the company-managed Jira Software project.

comments: author: Muhanned Shahada
body: Hi [@Nikola Perisic](/t5/user/viewprofilepage/user-id/5166624)   
we are using JWM company-managed projects, so there is no solution or workaround to this issue?


author: Nikola Perisic
body: Hello [@Muhanned Shahada](/t5/user/viewprofilepage/user-id/5408570)

In that case, you can change the default issue type in JWM:

1. Click on Project Settings
2. Click on Issue Types
3. Click on the cog then edit issue types
4. Default Issue Type, change this to Epic
5. Click on Save

![Screenshot 2024-02-26 at 16.21.57.png](https://community.atlassian.com/t5/image/serverpage/image-id/308680i59280727D2B0C943/image-size/large?v=v2&px=999 "Screenshot 2024-02-26 at 16.21.57.png")


author: Muhanned Shahada
body: [@Nikola Perisic](/t5/user/viewprofilepage/user-id/5166624) I did that but when i go to list view, it still shows me story as default.. That is the problem i am facing, i thought changing it default in the project settings would change it in the list, board view but it doesn't seem to be the case

![Captura de pantalla 2024-02-26 a las 16.25.31.png](https://community.atlassian.com/t5/image/serverpage/image-id/308682i4AED473FD87D5E46/image-size/large?v=v2&px=999 "Captura de pantalla 2024-02-26 a las 16.25.31.png")

![Captura de pantalla 2024-02-26 a las 15.32.40.png](https://community.atlassian.com/t5/image/serverpage/image-id/308681iD8D22DC37FF3F821/image-size/large?v=v2&px=999 "Captura de pantalla 2024-02-26 a las 15.32.40.png")


author: Nikola Perisic
body: [@Muhanned Shahada](/t5/user/viewprofilepage/user-id/5408570)

Check your issue type hierarchy. Which issue type is listed as number 1? You can check this by going to Settings -\> Issues -\> Issue type hierarchy


author: Muhanned Shahada
body: [@Nikola Perisic](/t5/user/viewprofilepage/user-id/5166624) This is what i have in my issues type hierarchy   
![Captura de pantalla 2024-02-26 a las 16.36.24.png](https://community.atlassian.com/t5/image/serverpage/image-id/308685i767A9048C0ACA7FD/image-size/large?v=v2&px=999 "Captura de pantalla 2024-02-26 a las 16.36.24.png")


author: Nikola Perisic
body: [@Muhanned Shahada](/t5/user/viewprofilepage/user-id/5408570) I see, this is defenlitly a bug. Even with the default issue type to be set as Epic and a workaround to create a new scheme and apply it, it reproduces the same result.

I will tag Atlassian as well and would like to hear what other people can say about this, if they are facing the same issue.


author: Muhanned Shahada
body: [@Nikola Perisic](/t5/user/viewprofilepage/user-id/5166624) Thank you, I look forward to hearing Atlassian support team on this bug.


Tags: atlassian

cloud

jira-work-management-cloud