[wp-meta] [Making WordPress.org] #7990: Improving close Workflow Keyword

[Making WordPress.org]

#7990: Improving close Workflow Keyword
-------------------------+-------------------------
 Reporter:  SirLouen     |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Trac         |   Keywords:  2nd-opinion
-------------------------+-------------------------
 The close keyword currently says:

 > The ticket is a candidate for closure with a disposition other than
 fixed (i.e. **wontfix**, **worksforme**, **invalid**, or **duplicate**).
 Often seen with **reporter-feedback** or **2nd-opinion**; otherwise, the
 ticket would have been closed in lieu of adding the **close** keyword.

 According to what I've been experiencing and what @desrosj suggested, the
 main purpose of close is:

 > Allowing a bit more time for additional details or opinions to be
 offered

 Nowadays, people have to waste their time going through all these `close`
 tickets that have not been activated, looking through them to conclude,
 again, what was concluded back in the day in most cases: It has to be
 closed.

 So I came up with a possible idea to improve the behaviour of the `close`
 keyword

 Thinking on the possibility of adding multiple keywords like:
 - `close-wontfix`
 - `close-invalid`
 - `close-worksforme`

 And adding a cronjob with a script that does this protocol:

 - Select all tickets with any of these keywords and pick the date when
 this keyword was added. If the date > 30 days from now, close the ticket
 with the given reason. Check that this is the last keyword added to the
 flow, if it's not the last, ignore.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7990>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org