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

Due date warnings now working - portfolio plan (roadmaps?)


I have a plan in jira cloud that is based off a filter. I am pulling in product capabilities, team level epics, and stories from multiple project spaces. I believe this is still part of our Portfolio subscription as we have not yet migrated to Align.

I have a team level epic that is in progress past the due date. I do not get an error or warning notification. 

I also tried to verify if warnings would work for a due date scheduled beyond a target due date and still I do not get a warning.

Show warnings  is turned on in my view settings.

Does anyone know why this isn't working? please help.

Epic warning.jpg

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 03, 2020 • edited

Hello @Courtney M. Schkurko ,

The warning will be triggered if the issue is unresolved after the defined due date, and that would be based on a value being present in the resolution field. 

Can you check that epic (CVBLNXESW-581) to see if it has a value present in the resolution field, as it may have been closed and later re-open without the field being cleared and have the field set as resolved but is still in the InProgress status as described in the following KB article, that discusses what to look for in more detail:


It did not have a resolution, and the history shows the epic has not previously transitioned. 

I think it has something to do with our internal issue type schemes. I'm working with one our of internal Jira administrators to try to resolve. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events