Yearly JIRA cleanup

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Yearly JIRA cleanup

michaelo
Hi folks,

after at least one year of silence, I'd like to perform another JIRA
issue cleanup for issues which have been not touched for more than three
years.

Query:
https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuetype%20DESC%2C%20created%20DESC

Stats:

567 issues not touched for more than three years
of which
* 68 have fix version set
* 36 were already reopened, should they be excluded?
* 1 in progress by Karl

Type breakdown:
* 200 bugs
* 164 improvements
* 72 new features
* 6 subtasks
* 13 tasks
* 12 wishes

If there are issues still valid for you please leave a comment on the
issue and they will not appear in the query anymore.
Please also raise your voice if you have anything to discuss.

If the issue is not modified or no objection has been raised, I will
autoclose those issues with a comment by 2019-12-30.

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

michaelo
Am 2019-12-08 um 13:55 schrieb Maarten Mulders:
> Hi Michael,
>
> Great initiative. After logging in to JIRA, accessing your link shows
> "The requested filter doesn't exist or is private."
> This means I'm not able to verify whether there are issues in that list
> that are valid for me.
> Is there another way to find those issues?

Apologies, here is the proper filter:
https://issues.apache.org/jira/issues/?jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC

I forgot to remove the filter id for my custom saved search.

Michael

> On December 8, 2019 at 13:50, Michael Osipov wrote:
>
>> Hi folks,
>>
>> after at least one year of silence, I'd like to perform another JIRA
>> issue cleanup for issues which have been not touched for more than
>> three years.
>>
>> Query:
>> https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuetype%20DESC%2C%20created%20DESC 
>>
>>
>> Stats:
>>
>> 567 issues not touched for more than three years
>> of which
>> * 68 have fix version set
>> * 36 were already reopened, should they be excluded?
>> * 1 in progress by Karl
>>
>> Type breakdown:
>> * 200 bugs
>> * 164 improvements
>> * 72 new features
>> * 6 subtasks
>> * 13 tasks
>> * 12 wishes
>>
>> If there are issues still valid for you please leave a comment on the
>> issue and they will not appear in the query anymore.
>> Please also raise your voice if you have anything to discuss.
>>
>> If the issue is not modified or no objection has been raised, I will
>> autoclose those issues with a comment by 2019-12-30.
>>
>> Michael
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Tibor Digana
In reply to this post by michaelo
Hi Michael,

What's up :-)
Thx for making the list of issues.
Pls give me one day to see it completely. I will get back to you tomorrow.

Cheers
Tibor17

On Sun, Dec 8, 2019 at 6:08 PM Elliotte Rusty Harold <[hidden email]>
wrote:

> Please don't. There are certainly some real and important issues in
> there. More importantly, users spent a great deal of effort and time
> to file those. Bulk closing them tells those users we don't value
> their feedback or effort. It is useful to triage these issues and
> consider them individually. Doubtless many of these issues are already
> fixed, moot, or things we expressly chose not to do. However this
> should be decided case by case. We can't simply close our eyes and
> pretend they're all irrelevant.
>
> On Sun, Dec 8, 2019 at 7:50 AM Michael Osipov <[hidden email]> wrote:
> >
> > Hi folks,
> >
> > after at least one year of silence, I'd like to perform another JIRA
> > issue cleanup for issues which have been not touched for more than three
> > years.
> >
> > Query:
> >
> https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuetype%20DESC%2C%20created%20DESC
> >
> > Stats:
> >
> > 567 issues not touched for more than three years
> > of which
> > * 68 have fix version set
> > * 36 were already reopened, should they be excluded?
> > * 1 in progress by Karl
> >
> > Type breakdown:
> > * 200 bugs
> > * 164 improvements
> > * 72 new features
> > * 6 subtasks
> > * 13 tasks
> > * 12 wishes
> >
> > If there are issues still valid for you please leave a comment on the
> > issue and they will not appear in the query anymore.
> > Please also raise your voice if you have anything to discuss.
> >
> > If the issue is not modified or no objection has been raised, I will
> > autoclose those issues with a comment by 2019-12-30.
> >
> > Michael
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> --
> Elliotte Rusty Harold
> [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

stephenconnolly
In reply to this post by michaelo
On Thu 12 Dec 2019 at 17:31, Robert Scholte <[hidden email]> wrote:

> IIUC since Jira uses the ASF LDAP, there's no extra need for Brian to do
> this anymore. All should be in place by now.
>

I think we have some crazy permissions that Brian manages. Ldap just fixes
the account name to match across systems AIUI

>
> thanks,
> Robert
> On 12-12-2019 15:20:24, Stephen Connolly <[hidden email]>
> wrote:
> On Mon 9 Dec 2019 at 20:53, Elliotte Rusty Harold
> wrote:
>
> > On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote:
> > >
> > > Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> > > > Please don't. There are certainly some real and important issues in
> > > > there. More importantly, users spent a great deal of effort and time
> > > > to file those. Bulk closing them tells those users we don't value
> > > > their feedback or effort. It is useful to triage these issues and
> > > > consider them individually. Doubtless many of these issues are
> already
> > > > fixed, moot, or things we expressly chose not to do. However this
> > > > should be decided case by case. We can't simply close our eyes and
> > > > pretend they're all irrelevant.
> > >
> > > Hi Elliotte,
> >
> > > We have almost 2000 open issues. How would you reasonably sieve between
> > > them? even if you allocate 10 min per ticket, you would need two months
> > > of work to triage them.
> > >
> >
> > Use the time we have to fix as much as we can. Leave the rest open.
> > Some will never be touched but some will be when someone encounters
> > the same problem and finds the bug again. It's better to leave it open
> > and unaddressed than to close it without giving it a fair look.
> >
> > As to time spent triaging, it's worth considering whether permissions
> > could be opened up further. Right now, almost anyone can file a bug
> > but few people can resolve and close them. I can't, for example, even
> > when I see one that's clearly no longer relevant. :-(
>
>
> As soon as Brian fixes your JIRA permissions you’ll be able too... your
> committer status is only freshly minted! (welcome/congrats)
>
> Another issue is the lack of a clearly defined process for triage. We
> should document what we mean by triage and what outcomes we expect. That
> could even include closing stale issues after a check for active reporters
>
> >
> >
> > --
> > Elliotte Rusty Harold
> > [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> > --
> Sent from my phone
>
--
Sent from my phone
Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Elliotte Rusty Harold
NVM, I seem to have access now. I think I just needed to logout with
my old credentials and back in with the new ones.

On Fri, Dec 13, 2019 at 9:56 AM Elliotte Rusty Harold
<[hidden email]> wrote:

>
> On Thu, Dec 12, 2019 at 6:56 PM Stephen Connolly
> <[hidden email]> wrote:
> > I think we have some crazy permissions that Brian manages. Ldap just fixes
> > the account name to match across systems AIUI
> >
>
> That's probably true. As of an hour ago, I did not seem able to close issues.
>
>
> --
> Elliotte Rusty Harold
> [hidden email]



--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Elliotte Rusty Harold
In reply to this post by michaelo
One thing we should try going forward is be more ready to won't fix
and close bugs and RFEs we disagree with. I've seen several examples
where the comments indicate the maintainers did not agree with the
issue, but it still wasn't closed. E.g.

https://issues.apache.org/jira/browse/SUREFIRE-1227

Closing an issue is not irrevocable. Issues can always be reopened, if
the reporter or anyone else disagrees. Indeed it is more respectful to
reporters to be politely honest with them about our true objections,
rather than simply ignoring the issue and not responding.

On Fri, Dec 20, 2019 at 6:29 AM Elliotte Rusty Harold
<[hidden email]> wrote:

>
> While working through the bugs I found this interesting bit of history:
>
> https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
>
> It seems like we've been here before. Some of the bugs that were
> autoclosed then were reopened and are now scheduled for autoclose
> again. Any thoughts about how we might update our processes to avoid
> getting into this situation again?
>
> On Sun, Dec 8, 2019 at 7:50 AM Michael Osipov <[hidden email]> wrote:
> >
> > Hi folks,
> >
> > after at least one year of silence, I'd like to perform another JIRA
> > issue cleanup for issues which have been not touched for more than three
> > years.
> >
> > Query:
> > https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuetype%20DESC%2C%20created%20DESC
> >
> > Stats:
> >
> > 567 issues not touched for more than three years
> > of which
> > * 68 have fix version set
> > * 36 were already reopened, should they be excluded?
> > * 1 in progress by Karl
> >
> > Type breakdown:
> > * 200 bugs
> > * 164 improvements
> > * 72 new features
> > * 6 subtasks
> > * 13 tasks
> > * 12 wishes
> >
> > If there are issues still valid for you please leave a comment on the
> > issue and they will not appear in the query anymore.
> > Please also raise your voice if you have anything to discuss.
> >
> > If the issue is not modified or no objection has been raised, I will
> > autoclose those issues with a comment by 2019-12-30.
> >
> > Michael
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> --
> Elliotte Rusty Harold
> [hidden email]



--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]