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,373
Community Members
 
Community Events
176
Community Groups

How to add column "Epic Link" to the Plans

Hello I would like to add Jira native field "Epic Link" to the Plans column. Same time I excluded Epics from the Plan to just track Stories and other issues from this level.

This column is nto visible for me.

Additionally I cannot add other columns like: Reporter, Created etc...2022-02-17 21_13_52-Resources allocation - Advanced Roadmaps - JIRA — Mozilla Firefox.png

2 answers

Thank you. That's indeed strange some core Jira fields are not accessible in this view.

What I did as a workaround I created custom field and this field copies the name of the Epic - inside of the Epic and it's children.

0 votes
Curt Holley Community Leader Feb 17, 2022

Hi @Anita Domańska 

Yes, Epic link and other Epic or Version related fields are not supported/available in Advanced Roadmaps to display as a field/column. This is because they serve other key components of the Advanced Roadmaps views/hierarchy/grouping.

I must confess I've never noticed that fields like Reporter or Created are not available.. I don't know the reason why, but at a guess, because they are not (usually) fields that ever change.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events