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

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
4,459,450
Community Members
 
Community Events
176
Community Groups

Is the parent link field dependent on having a Portfolio license?

My organization has been using Portfolio but we are planning to stop using it and will drop the license. We have a number of epics that are linked to Initiatives. Will eliminating the Portfolio license also remove the Initiative issue type and the parent link field? Trying to determine whether I will have to implement a different approach to linking epics to their parent initiatives.

1 answer

1 accepted

0 votes
Answer accepted

Yes - the defined hierarchy requires Portfolio to be available.  Without the plugin, you can't have an additional hierarchy level above Epic.

You could still have an issue type called Initiative, and link to it using Linked Issues (using a parent/child link type). 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events