[wp-meta] [Making WordPress.org] #296: Prevent re-opening a ticket closed as fixed on a closed milestone
Making WordPress.org
noreply at wordpress.org
Sun Jan 26 18:33:01 UTC 2014
#296: Prevent re-opening a ticket closed as fixed on a closed milestone
------------------------+------------------
Reporter: nacin | Owner:
Type: enhancement | Status: new
Priority: normal | Component: Trac
Keywords: needs-patch |
------------------------+------------------
This comes up sometimes on Core Trac. Someone disagrees with a change, or
finds a change to be incomplete or buggy, or has an additional suggestion
for a change. They then re-open the ticket. The problem is, the ticket is
already closed as "fixed," and on a completed milestone. Someone has to
then come along and ask them to make a new ticket (usually with the same
exact information as their comment), which is annoying for everyone
involved.
We should prevent tickets from being re-opened when they are closed on a
completed milestone. This isn't particularly easy to do via configuration
or templating, but a little JS seems like it'll handle this situation
perfectly fine.
I think we could also place a box on the bottom of the ticket (possibly
next to a visually disabled "reopen" option) to create a new ticket
instead, referencing this one in the process.
Bug gardeners should still be able to re-open a ticket.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/296>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list