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 not Displayed in Plan


Was adding issues (stories) to an Epic and went to refresh my plan that the epic is included in. It shows previously added issues in the plan, but is not reflecting the newly added issues in the plan. 

Checked the Fix Version and confirmed that all checks out, checked plan sources, nothing is excluded, all filters are cleared out. When I view at the program level and attempt to sync it says completed but the child issues count value remains constant and hasn't updated to reflect the newly added issues like it does in the Release view or in the Epic record view itself. 

Have tried all troubleshooting recommendations, does not seem to be content tagging, or filtering, etc... related. My plan isn't updating to reflect new issues and I don't know why. Jira Help_Epic View.jpgJira Help_Plan View.jpgJira Help_Release View.jpg

Jira Help_Program View.jpg

1 answer

1 accepted

0 votes
Answer accepted

Executed a workaround. Cloned the two Stories that refused to show up in my plan and the cloned records popped right in. Closed the previous (637/638) records as duplicates and not working due to some kind of server issue. 

Don't know what the root cause of this issue was, but suffice to say my planning is back on track. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events