This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
I'm one of the core Spring committers, and even I don't get to close issues
Juergen closes all of the issues that have been resolved for a particular version just before that version is actually released. I'll take it up with him when next I see him, but in the interim you could I guess try filtering on anything that isn't marked as resolved.
I don't think there is an easy way to do this at this point with the current JIRA instance. Basically, we wouldn't want users to start closing issues by accident . Ideally, a user should be able to close his own issues but that requires some special JIRA permissions..
One suggestion for the moment is to comment on the issue that they are resolved - the should be closed fairly soon afterwards.