Ignore slack mentions of old tickets

[knutsp]

If a very old ticket, closed years ago, is mentioned in Slack (or else?) a comment referring to the mention is created on Trac(s).

Please avoid, as it's confusing. No need to see this. Actually embarrassing :)

Detect age by very old open date and now closed, or time (years) since last closed.

[dd32]

@knutsp Can you provide an example of where it's gone wrong? Some extra context might help get something more actionable

For reference, lots of discussions do refer back to very old tickets, and so pulling them into Slack and cross-referencing the conversation is useful (The slack posts on Trac shouldn't trigger emails)

It should only expand # followed by 4 or more digits to work around GitHub references or mentioning things like #1... #2...

[obenland]

Replying to dd32:

For reference, lots of discussions do refer back to very old tickets, and so pulling them into Slack and cross-referencing the conversation is useful

It should only expand # followed by 4 or more digits to work around GitHub references or mentioning things

That's how I feel about it too. Though I think I'd allow 3-digit ticket numbers to account for meta etc.

[obenland]

In 7347:

Trac: Ignore two-digit tickets and changesets

Props knutsp.
Fixes #3650.

[knutsp]

Three digits are common, too:
​https://core.trac.wordpress.org/ticket/249#comment:8

[knutsp]

Three digits:
​https://core.trac.wordpress.org/ticket/185#comment:31

[dd32]

In 11582:

Slack: Don't post a "This ticket was mentioned in.." on old closed Trac tickets.

This still posts the Ticket reference to Slack, but if the ticket has been has been closed over 2 years avoids littering it with references that were probably not about it.

See the ticket for an example of where a GitHub reference posted to a ticket that had been closed for 14 years.

Fixes #3650.