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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Possible to bypass the EPIC level and link story to issue type above Epic (Portfolio Hierarchy)?


This is our current hierarchy with Portfolio

  • Initiative
  • Feature
  • Epic
  • Story
  • SubTask

I have a request from a team that doesn't want to use Epics, but link Stories directly to Features.  I removed Epic from the project's issue type scheme and added a parent link on the story screen to link to the next level up in the hierarchy.  When I try to use the parent link on the story it expects a Epic link. 

I understand that the relationship between a story and the epic is an out-of-the-box one that used an Epic Link and not a generic link.

Is there a way to get past this or this the Epic->Story->SubTask Hierarchy something that cannot be altered?

We currently have Portfolio.  Would something like Structure allow us to do something like this? 

Can Portfolio and Structure live happily on the same instance of JIRA?

Possible to have multiple hierarchies within JIRA?



1 answer

0 votes

Hi @Tom Gross ,

I haven't personally done this in a live environment before so I would advise testing it first to ensure the functionality is as expected, but I was able to do this by adding in Feature to the same hierarchy level as Epic, and then removing the Epic Link field from my project's screens.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events