Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Enabling Epics in Jira Project Management Template

The Jira Project Management template does not natively allow Epics. I'd like to add it. I've found a way to make it appear, but it doesn't function as I would want.

How I got the Epic option to appear

  1. I went Project Settings > Issue Types > Edit Issue Types > Issue Type Schemes.
  2. Searched for my project name and clicked Edit
  3. Dragged Epic to the column Issue Types for Current Scheme

This give you option to choose "Epic" when you click the create button. But it will not work because it requires Epic Name as a field. That problem is reported and partially solved here: https://community.atlassian.com/t5/Jira-Software-questions/Cannot-create-Epic/qaq-p/707042 I believe it is incomplete, so to further solve this problem

  1. Clicked Field Configuration > Default Field Configuration
  2. Searched for "Epic Name" and clicked "Screen"
  3. Clicked the checkbox for my project name "Create Issue"

 

Finally

  1. Go to Issue Layout
  2. Click on <<project name>> Project Management Edit/View Issue Screen
  3. Add Epic Name

Now "Epic Name" should appear as a required field when you create an Epic.


Why it doesn't work

 

1. In list view, you can create tasks that are under an epic you created. As soon as you refresh the page, it doesn't nest underneath the epic anymore.Screen Shot 2022-11-09 at 9.54.53 PM.png

Screen Shot 2022-11-09 at 9.55.21 PM.png

2. In other boards, you don't need to define "Summary" and an "Epic Name". This is duplicate effort.

Thanks for the help,

-Ed

1 answer

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 10, 2022

Hello @Edward Young 

Welcome to the community.

The problem with issues not staying nested under the Epic is a known issue. You can watch that issue here:

https://jira.atlassian.com/browse/JWMCLOUD-266

Concerning your second issue, what are you referencing for "other boards"? Are you referencing Company Managed projects or Team Managed projects? 

Summary and Epic Name are currently both required for Epic issues within Company Managed projects. Epic Name is not required for Epic issues within Team Managed projects. Atlassian is currently working on realigning this so that Epics are the same for both types of projects. That is discussed here:

https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 20, 2022

As per the earlier comments on the issue, you need to open a case with Atlassian Support to get the fix applied to your environment.

https://support.atlassian.com/contact/#/

Alexandre Denault
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Sep 05, 2023

Is there still a way to request this fix? We are having this issue on our boards. Unfortunately, when I try to reach out to Atlassian using the link above, I get redirected to the community boards.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 05, 2023 • edited

@Alexandre Denault 

Welcome to the Atlassian community.

Are you on a Free plan or a paid plan?

Using the support link I provided works for Jira Administrators on paid plans. Those on Free plans are not entitled to direct Atlassian support.

Additionally, I believe the fix has been rolled out. The need to request it was only prior to final roll out.

If you are encountering what you think is the same problem, can you start a new Question and provide details about your environment/situation? Include a link to this existing post if you think you problem is the same as the one discussed here.

Alexandre Denault
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Sep 05, 2023

We are on a paid plan, and I am a Jira administrator, but not an Atlassian administrator, which is most likely needed to send a support request.

I've continued working with the JWM lists and have noticed quite erratic behaviour when expanding epics. When expanding an epic, it will often "transform itself" to a task and not list that tasks linked to the epic.

I'm going to setup a new test project, with dummy data. If I still get the behavior, I will post a new questions.

Thanks,

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events