Closing inactive issues
Hi all, We have currently almost 1000 issues for the Log4j project alone. Let us be honest, most of these issues will **never** be solved, we barely have time for the issues reported against the current Log4j version. What do you think about automatically closing as "Won't Fix" or "Abandoned" the issues without any activity in the last 2 years[1]? The issues will not disappear from JIRA, but we will no longer spend time on them (we don't look at them anyway). Piotr [1] https://issues.apache.org/jira/browse/LOG4J2-3079?filter=-4&jql=project%20%3D%20LOG4J2%20AND%20resolution%20%3D%20Unresolved%20AND%20updated%20%3C%3D%20-104w
Re: Closing inactive issues
Even though it is unfortunate, I can understand where you are coming from and I agree with you. Such forsaken tickets even started piling up in GitHub Issues too. We should indeed trim them as we see fit. After all, nothing is lost, everything is archived. Users can re-open old tickets if needed. On Wed, Apr 24, 2024 at 3:20 PM Piotr P. Karwasz wrote: > Hi all, > > We have currently almost 1000 issues for the Log4j project alone. > > Let us be honest, most of these issues will **never** be solved, we > barely have time for the issues reported against the current Log4j > version. > > What do you think about automatically closing as "Won't Fix" or > "Abandoned" the issues without any activity in the last 2 years[1]? > The issues will not disappear from JIRA, but we will no longer spend > time on them (we don't look at them anyway). > > Piotr > > [1] > https://issues.apache.org/jira/browse/LOG4J2-3079?filter=-4&jql=project%20%3D%20LOG4J2%20AND%20resolution%20%3D%20Unresolved%20AND%20updated%20%3C%3D%20-104w >
Re: Closing inactive issues
Periodically I have tried to go through old issues and close those that I know will get no activity. I’d prefer to do that than just close them all. Now that Jira is locked down at least the list of issues there will never grow. In doing that I would actually recommend creating an issue at GitHub for any issues that should remain active (even if the contents are just a link to Jira) and still close it in Jira. So in the end all the Jira issues should be closed. Ralph > On Apr 24, 2024, at 6:18 AM, Piotr P. Karwasz wrote: > > Hi all, > > We have currently almost 1000 issues for the Log4j project alone. > > Let us be honest, most of these issues will **never** be solved, we > barely have time for the issues reported against the current Log4j > version. > > What do you think about automatically closing as "Won't Fix" or > "Abandoned" the issues without any activity in the last 2 years[1]? > The issues will not disappear from JIRA, but we will no longer spend > time on them (we don't look at them anyway). > > Piotr > > [1] > https://issues.apache.org/jira/browse/LOG4J2-3079?filter=-4&jql=project%20%3D%20LOG4J2%20AND%20resolution%20%3D%20Unresolved%20AND%20updated%20%3C%3D%20-104w
