Items with Release Set Appearing Under "Unassigned" When Grouping by Release in Advanced Roadmap

[Diluka Talagala]

I'm using Advanced Roadmaps and have set the view to group by Release. However, I'm noticing that some items are appearing under "Unassigned", even though they clearly have a Fix Version set.

I've already checked that all the child items have a release set.

[Trisha Griffis]

This behavior usually points to configuration issues rather than a bug. Here are the most common reasons and how to fix them: 

Possible Causes & Fixes 

1. Fix Version Field Hidden

If the Fix Version field is hidden in the issue’s field configuration, Advanced Roadmaps can’t detect the release—even if one is set.

Fix: Go to Jira Admin → Issues → Field Configurations, locate your configuration, and ensure Fix Versions is visible.

2. Release Not Included in Plan Scope

Your plan may not include the relevant release in its scope, causing those issues to be grouped as “Unassigned.”

Fix: Under your plan’s settings, navigate to Issue sources → Edit issue sources, then make sure to include all relevant releases in the “Releases” step.

3. Hierarchical Display Constraints

Sometimes when the plan’s hierarchy shows multiple levels, parent issues may appear under “Unassigned” even when they appear in release-specific swimlanes. This often happens if child issues are missing release assignments.

Fix: Try limiting the displayed hierarchy levels or ensure child issues also have their releases properly set.

Response provided by Jer-nee Consulting, a Gold Atlassian Solutions Partner. If you need additional guidance feel free to let us know. You can book a call here