[policy, no patch] Adopt a set of guidelines for closing stale bug reports

Created on 2 July 2020, almost 4 years ago
Updated 21 April 2023, about 1 year ago

As part of the Bug Smash Initiative → , we are triaging issues that are marked "Postponed (maintainer needs more info)", or tagged with "Needs steps to reproduce" and "Needs screenshots".

We had a discussion in Slack #bug-smash about guidelines for when it is OK to close an old issue and wanted to record that as well as opening it up for wider feedback.

Consensus on Slack was that if an issue meets these three criteria, it should be closed:

  1. Report consists only of an error or description of an error with no steps to reproduce
  2. Someone replied asking for steps to reproduce >6 months ago
  3. No steps were provided and/or it is only reproducible in the reporter's site

This proposal only applies to a relatively narrow set of issues, and many of these are already closed as part of the initiative triage. So I think there is a more broad discussion to be had about stale issues and not just ones that meet these somewhat obvious criteria.

The idea of automating this came up as well, which is something that has been discussed before in #156704: Dealing with "postponed (maintainer needs more info)" issues → and #1230642: Automatically mark "postponed (maintainer needs more info)" issues to "closed (cannot reproduce)" → .

🌱 Plan
Status

Fixed

Version

10.1 ✨

Component
Other  →

Last updated about 16 hours ago

Created by

🇦🇺Australia pameeela

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇳🇿New Zealand quietone New Zealand

    Reading #11 and #16 I decided to look at the evidence. There are 25 issues tagged bugsmash and accessibility that have been closed for reasons other than fixed.

    won't fix: 2
    works as designed: 7
    cannot reproduce: 6 (includes several IE 11 issues)
    outdated: 10 (includes several IE 11 issues)

    I opened all the issues and read how they were closed. I didn't find that any of them were closed improperly. I do agree with @pameeela in #14 that the Bugsmash triagers are "taking a cautious approach to this and treating every issue with care.".

    I have added the proposed text to the initiative docs, https://www.drupal.org/community-initiatives/bug-smash-initiative/issue-... →

  • Status changed to RTBC over 1 year ago
  • 🇧🇪Belgium borisson_ Mechelen, 🇧🇪

    The concerns in #11 are very valid, but as remarked in #24 and #25 we've been very careful about this in the past and will continue to do so.

    I think writing down, and consistently following this policy, while still being careful is a good improvement in the maintenance of the issue queues.

  • 🇫🇮Finland lauriii Finland

    +1 for the proposed policy, as a more manageable issue queue benefits everyone by increasing our efficiency. I believe that it's essential for us to emphasize that closing stale issues doesn't mean disregarding bugs or problems. Issues are being closed because they are lacking next steps due to insufficient information.

    We should always respect reported problems and strive to understand them. However, if we cannot proceed on an issue due to inadequate information, it holds little value in the queue. While #11 brings up valid concerns, I don't believe that maintaining a queue filled with unactionable issues addresses those issues.

  • Status changed to Needs work about 1 year ago
  • 🇹🇼Taiwan g-brodiei

    Saw this issue from bug smash initiative channel from @quietone to check wordings on policy page.

    +1 on the policy change. I’ve read through the threads and notice a slight wording diff on the policy page.

    On the issue summary:
    If the stale issue meets these criteria, it should be closed:

    On policy page → :
    if an issue meets these three criteria, it should be closed:

    I believe the word `three` would make it clearer for future readers (not native English speaker) to understand the criteria, thanks!

  • Status changed to Needs review about 1 year ago
  • 🇳🇿New Zealand quietone New Zealand

    Thanks!

    I have updated the page → .

  • Status changed to RTBC about 1 year ago
  • 🇹🇼Taiwan g-brodiei

    Checked the page → , wording changed as suggestion, thanks!

    Set to RTBC

  • Status changed to Fixed about 1 year ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024