Closed issues appear in active sprint but have never been assigned to it

There are issues which have been closed some time ago and now appear in the current sprint.

For example, there is an issue which as been resolved as "Won't fix" and closed on Jan 7th. It was not assigned to any sprint at that time and has not been touched since then.

However, now it appears in the current April sprint. Why? It has never been explicitly assigned to this sprint as you can see from the issue history.

2 answers

We had an issue where closed issues that had no sprint assigned showed up in the Active Sprints board.  So I just added the following JQL to the board's filter query: 

AND (sprint is not EMPTY OR status != Closed)
0 votes
Anna Cardino Atlassian Team Apr 24, 2014

Hey there, Thomas.

Have you tried re-indexing when you noticed this at first? One of the possibilities to this is that your JIRA might be in the inconsistent state which causes Closed issues to appear in the current sprint.

Also, can you check on the following:

  • Quick Filter of the board
  • Scrum Board Filter

If you still have issues and need urgent attention, kindly raise a ticket in support.atlassian.comfor further follow up.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Apr 22, 2018 in Jira Software

How-to setup a secured Jira Software 7.9.0 on Ubuntu 16.04.4 in less than 30 minutes

...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...

1,763 views 14 13
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you