Candidates for Closure requirements?

[SirLouen]

Following from #8046

What makes a ticket a "Candidate for Closure"?

As we can see here (​report), there are tickets without close living there.

I thought its a matter of time (auto-staleness like in GH), but there are new ticket and modified tickets there recently so this is discarded

Also thought that maybe a close was posted in the past, but some of them don't have received a close tag ever. Also, a possibility was a Reopened ticker, but again there are tickets without close tag, and never closed.

And all of them are Awaiting Review.

So I can't figure out what is the condition tha triggers this.

[dd32]

@SirLouen Some things are better as a Slack discussion, the Core team manages their own reports, you don't need to ask Meta for that.

Tickets in the $COMPONENT component

SELECT
  CASE
  WHEN milestone LIKE '_.%'
  THEN 'Slated for Next Release'
  WHEN milestone = 'Awaiting Review' AND (keywords LIKE '%reporter_feedback%' OR keywords LIKE '%close%' OR keywords LIKE '%2nd_opinion%')
  THEN 'Candidates for Closure'
  WHEN milestone = 'Awaiting Review'
  THEN 'Tickets Awaiting Review'
  WHEN strftime("%%s", current_date) - 31536000 >= changetime / 1000000
  THEN 'Tickets Not Modified in a Year'
  WHEN keywords LIKE '%feedback%'
  THEN 'Tickets Needing Feedback'
  WHEN keywords LIKE '%has_patch%'
  THEN 'Tickets with Patches'
  WHEN type = 'defect (bug)'
  THEN 'Unpatched Bugs'
  ELSE 'Unpatched Enhancements'
  END as __group__,
....

  CASE
  WHEN keywords LIKE '%needs_unit_tests%'
  THEN 'needs-unit-tests'
  WHEN keywords LIKE '%needs_docs%'
  THEN 'needs-docs'
  WHEN keywords LIKE '%close%'
  THEN 'close'
  WHEN keywords LIKE '%needs_review%'
  THEN 'needs-review'
  WHEN keywords LIKE '%dev_feedback%' OR keywords LIKE '%2nd_opinion%'
  THEN 'dev-feedback'
  WHEN keywords LIKE '%reporter_feedback%'
  THEN 'reporter-feedback'
  WHEN keywords LIKE '%commit%'
  THEN 'commit'
  WHEN keywords LIKE '%tested%'
  THEN 'tested'
  WHEN keywords LIKE '%has_patch%'
    OR keywords LIKE '%needs_testing%' AND keywords NOT LIKE '%needs_patch%'
  THEN 'has-patch'
  WHEN keywords LIKE '%early%'
  THEN 'early'
  ELSE ''
  END as workflow,

[SirLouen]

Replying to dd32:

@SirLouen Some things are better as a Slack discussion, the Core team manages their own reports, you don't need to ask Meta for that.

Ok, since I saw this Trac component here, I assumed this is a Meta thing.
Btw, Thanks for the info; it's very useful.

[desrosj]

I came across this ticket looking for a completely different GitHub issue.

I just wanted to note a recent change that is relevant to this request in case someone comes across this in the future.

I recently adjusted the Component Maintainer and Bug Gardener groups in Trac to grant the REPORT_SQL_VIEW capability. Previously only the Committers and Trac administrators were able to view the underlying SQL query for a given report.

This will hopefully result in fewer requests from contributors who are trying to better understand a report, or at least widen the pool of contributors who can provide an answer.