Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JIRA creates by default a Task, even if Epic is set by default

Timur April 2, 2025

Hello!

 

I changed everywhere the default issue type hierarchy, 

Screenshot 2025-04-03 at 00.16.20.png Screenshot 2025-04-03 at 00.15.07.png Screenshot 2025-04-03 at 00.14.54.png Screenshot 2025-04-03 at 00.14.31.png

BUT still the default issue is a Task, not an Epic:

Screenshot 2025-04-03 at 00.16.54.png Screenshot 2025-04-03 at 00.16.51.png

Any ideas why?

Thanks a lot!

BR

1 answer

1 vote
John Funk
Community Champion
April 2, 2025

Hi Timur,

The default issue type is not based on the hierarchy. If you go into the Issue Type Scheme, you have the ability to set which issue type is your default. In the absence of that, it will use the one at the top of the list. 

Now, having said all of that, the system tends to default to the last issue type you used to create a new issue. Why? I don't know - just Atlassian's way of helping you out in their mind I guess. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, confluence, loom, atlassian intelligence, ai notes, ai-powered meeting notes, atlassian community events, ace, confluence ai, loom ai integration, ai note-taking, atlassian ai features, team '25, atlassian live learning, confluence automation

Unlock AI-powered meeting notes: Join our live learning session! 📹

Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.

Register today!
AUG Leaders

Atlassian Community Events