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

Resolved Epics Still Appearing in Portfolio

I have created a Portfolio plan based off of a board.  There are Epics in the board that have been marked as done and have a resolution associated to them.  Additionally, they have all been "Marked as Done" in the Jira Backlog view.  These Epics are persistent and still visible in Portfolio even though everything associated to them is marked as resolved. 

I am looking for some advice to see what setting I might have missed or where to start troubleshooting.  I do not want to have to exclude these Epics, I would rather they just fall off once completed. 

Thank you.

1 answer

Turns out that the statuses are buried under More.  Once you turn off Done statuses it will show you the view you are expecting.  Found the answer here: https://community.atlassian.com/t5/Portfolio-for-Jira-questions/View-Resolved-issue-in-Portfolio/qaq-p/789200

 

Now the problem I am running into with this solution is that it negates the progress bar since nothing Done is being shown.  Which makes that whole column useless.  There has to be a better way to resolve this.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events