If there was a small number of issues, doing a more thorough cleaning job would make sense, but I'd rather spend our brain energy in fixing real issues than tracking commits which closed an old one. In an ideal world the person who opened the issue would make some of the work required for closing it too.
The process you have been following so far looks great to me. Mihai ________________________________ From: jensen <[email protected]> Sent: Sunday, January 25, 2026 7:43 PM To: [email protected] <[email protected]> Subject: How to handle JIRA tickets that have been fixed but not closed Hi Calcite Community, Since Calcite has been around for a long time, many JIRAs have actually been fixed but not closed [1]. Now, I'd like to discuss how we should handle these JIRAs. For example, should we submit an additional PR to provide test cases to prove that the JIRA has been fixed? Should we find a commit that directly or indirectly fixes the issue as additional information (this may not be mandatory)? If we need a PR, do we need some minor specifications? For example, should we still maintain strict consistency between the PR title/commit message/jira title? Should we include the commit that fixes the issue (if found) in the PR and explain that this is just adding test cases? So, I'd like to ask how we can better handle these types of JIRAs. Best regards, Zhen Chen [1] https://github.com/apache/calcite/pull/4763
