Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Issues status set in Done does not show up in portfolio view


We are using Portfolio to view the overall tree structure of the EPIC and having overall status helped.

In the Plan setting, under issue source, there are days we can include completed issues. However, we are seeing that some of the status done within a month are not visible. Despite that, the days of completed issues have been set to 200 days.


Is the trigger for showing the done ticket is by resolved dates?


The tickets that show in the Portfolio are the one that has resolved dates and the tickets that did not show in the portfolio are the one that does not have the resolved dates.

It seems the portfolio lists are trigger by the resolve dates, to fix this how can we trigger the resolved dates?

1 answer

Found the reason why done status Jira does not show up in Portfolio view.

It all comes down to if Jira ticket has resolved date or not. Portfolio requires this for filter.

The Resolved Date is trigger when you have post-function to set the field resolution to non-null.

What we were doing at the beginning is to set the field resolution after status done is set to trigger project automation on the field resolution to set to done. By doing it this way, Jira system does not interpret this as the issue is resolved properly, hence there will be no resolved date in place.


I am not sure if this can translate into an improvement or fulfill as a bug fix.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events