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!


Unable to find unassigned issues

Jira Advanced Roadmaps says I have 12, 15, 14, 9, 7 unassigned issues in the next few sprints when I click on the sprint name. This is surprising, because I frequently look at these upcoming sprints in the backlog view for planning.

Unfortunately, when I try any of the following methods to find them, no dice:

  • CTA on hover modal: View sprint in Jira
  • Filter issues by this sprint, and status = unassigned
  • Backlog quick filter for unassigned 
  • JQL search: sprint = "8-31-2020" and assignee is EMPTY

I tried assigning all epics and initiatives. I looked for subtasks, but couldn't find any. Are there any other places I should look? 

For now I'm trying to ignore it - but it's really distracting. 


Screen Shot 2020-08-25 at 2.14.55 PM.pngScreen Shot 2020-08-25 at 2.01.46 PM.png

1 answer

1 accepted

0 votes
Answer accepted
Rhys Christian
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 25, 2020

Hey Stephen,

Thanks for reaching out. It's fair to say this particular insight isn't easy to diagnose from the label. What this is really saying is: "There's x issues scheduled in the sprint but not assigned to it". This could simply be that stories or epics are scheduled across the sprint (based on dates) but isn't assigned to it. Cases like this are OK - we just provide the insight. This is also why your steps to investigate wouldn't help find the relevant issues.

To be honest the main reason for insight is less relevant now. Previously, capacity for sprints used to only consider stories assigned to the sprint, and wouldn't consider points from stories simply scheduled within the sprint timeframe. Following modifications to the calculation of planned capacity, we now also consider unassigned issues.

I hope this helps provide context around this. Please let me know if you have further questions or pains with this.



Thanks for the guidance, I found that Roadmaps is warning about my Epics and Initiatives that are happening during these sprints being unassigned to these sprints. This was not obvious to me initially since I didn't consider that Epics could belong to a sprint. 

Assigning them to individual sprints fixes the Unassigned count, but it also blows up my capacity plan because these large hierarchy issues are too big to fit in any one sprint. 

Allowing me to schedule an epic / initiative across multiple future sprints seems like it would fix this new issue, but I cannot do that from Advanced Roadmaps or the regular Jira interface. 

It would be nice if Jira automatically populated future sprints based on dates associated to the sprints, and dates associated to the epic / initiative. Then, based on capacity warnings, it would be easier to make appropriate planning adjustments by hiring team members to increase capacity and velocity, or pushing out epic / initiative start and end dates. 

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events