We are facing an issue in the Jira Plan where the majority of Done user stories associated with Epics are not visible, while only a few completed items are appearing.
We have already attempted the following troubleshooting steps:
This confirms that the issue is specific to completed (Done) user stories, not with issue visibility in general.
Currently, this is blocking our progress on critical projects, as we are unable to:
We require urgent support to identify the root cause and resolve this issue at the earliest.
Hello @Varun Shetty
AR is incredibly picky about the Resolution and Resolved Date fields.
If a story is in a "Done" status category but the Resolution field is actually empty or if the Resolution is set but the "Resolved" timestamp is missing the plan will often hide them because it considers the data "invalid." This often happens when teams move issues to Done via a bulk edit or a misconfigured automation that skips the proper workflow transition.
I’d start by running a JQL search on your board to see if these "ghost" stories appear:
statusCategory = done AND (resolution is EMPTY OR resolutiondate is EMPTY)
If they show up there, your workflow isn't sealing the deal on those issues, and AR is dropping them from the view.
If the data looks clean, the next culprit is often the View Settings.
If you have "Group by" set to something like Release, child issues (Stories) can sometimes vanish if the parent Epic has a Fix Version assigned but the Stories themselves do not. Try setting Group by to "None" and clearing all plan filters to see if they resurface.
One weird edge case. If you happen to be on a Jira version between 10.3 and 10.7, there is a known UI bug where child issues simply don't appear when using Dark Theme. Try switching to Light Mode just to rule out a CSS glitch.
If a brand-new plan built from the same source shows the stories immediately, you're likely looking at a plan-specific cache or indexing issue that a fresh start will solve.
@Arkadiusz Wroblewski Thank you for your response will check and get back to you by trying these steps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.