jverano, that is correct. Since the information wasn't being logged prior to the fix being implemented there is unfortunately no way to retrospectively uncover it. Hope this helps.

Regards,
Ian Dick,
Atlassian

I noticed this was fixed in 6.4.0.3, does that mean that once we upgrade only sprints that are closed after the upgrade will audit the user ? i.e. no way to see who closed the sprint prior to the upgrade?

This feature is in the works now. We understand it's a desirable feature to have and looking forward to getting it into Agile soon

Thanks for working on this Ian. My boss is keenly interested in this functionality as someone just closed our active sprint in the middle of our sprint con-call

This needs to be implemented. Along with the ability to re-open a sprint if needed.

We would also like to put in request for this to be prioritized in backlog soon.. Thanks!

@Atlassian: any news? We would really need that issue fixed, plus the corresponding https://jira.atlassian.com/browse/GHS-7804

Audit in Greenhopper is necessary like closing the sprint, deleting the sprint etc.

In large instance with may admins it will be a usual feature.

Also a feature to re open the closed sprints.

Clearly this is an important bug, one that this more important because there is no way to reopen a Sprint. It seems that an UX designer forgot that people do always make mistakes.

Don't try to argue about restoring from backup, these are ALL live systems and between the moment something happens and the moment that you discover the problem, people are doing things. The database restore use valid only for total-disasters, not for partial ones.

Anyway, finding who did it is not going to solve the problem.

We're also having major issues with this feature right now. This has happened twice within the last month. Both times, an active sprint was inexplicably closed, but definitely not by a user. With sprints randomly closing and the inability to re-open closed sprints (why?), the sprint feature is essentially unusable for us.