Renegade issue in a Sprint

[Robert Egan]

I just had a user who could not close their sprint because the system thought there was an issue that still had open sub-tasks. The issue it reported did indeed have two open sub-tasks, BUT it was absolutely not related to the sprint. It was not even in the same project, and had absolutely no dependencies that I could find (even using SQL on the issuelink table).

Since sprints appear to be defined by a JQL query (which only referenced the project for the sprint) I also did a full re-index (i.e. deleting the index folder on the server) and that did not fix it either. In the end, the developer responsible for the renegade issue deleted it, and that allowed the sprint to be closed.

So my question is: How can something like this happen? Is there anything I more I could have done to clean this up short of deleting the renegade issue?

[Brant Schroeder]

@Robert Egan You can add any issue to a sprint.  The JQL only defines what is shown on the board.  Next time this occurs just edit the issue and remove it from the sprint it accidentally got associated with.

[Robert Egan]

The problem was that no one actually added the issue to the sprint.