Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

"epic" is assigned to backlog in scrum board

송원재 I'm New Here Jun 10, 2021


my scrum team is using classic board to manage multiple projects.

currently we need to add next-gen project issues to our backlog.

and we have faced a problem in our backlog.



- there are epic 1/2/3 which are defined as "epic" type in next-gen project.

- those epics are assigned to our backlog!!

- and "issue" which are under the "epic" seems to be handled as "sub-task"!!

---> I think that those epic 1/2/3 should be assigned to EPICS which is on the left side of the backlog. and the "issue"s should be assigned to our backlog.


is there any configuration to solve this problem?

1 answer

1 accepted

0 votes
Answer accepted

Hello @송원재 

Welcome to the community.

There is not a configuration to solve this problem.

In Classic projects, the parent Epic information is stored in an issue's Epic Link field. The parent issue information for a Sub-task in stored in the Sub-task's Parent field.

In NextGen projects, the Epic Link field is not used. Instead the Epic information is stored in the Parent field in its child issues, just like the parent issue information is stored in a Sub-task's Parent field.

Currently JIRA Cloud does not support creating multiple boards for a NextGen project that behave like the NextGen project's board. So, if you create a board based on a saved filter that includes NextGen issues, it behaves like boards created for Classic projects. Because of that, it will interpret the link between an issue and its parent Epic as a "sub-task" link because the information is in the Parent field instead of the Epic Link field.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

233 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you