Making WordPress.org

Opened 5 weeks ago

Last modified 5 weeks ago

#8196 reopened defect (bug)

Meta Trac: Ticket #8185 vanished

Reported by: chealer's profile chealer Owned by:
Milestone: Priority: normal
Component: Trac Keywords:
Cc:

Description

At 2026-02-28T17:44:14Z, I filed Meta ticket #8185: “Tickets and ticket comments are not saved automatically”. Ironically, that very ticket has been missing since at least 2026-03-05T18:00:00Z. The URL simply yields a 404 error "Error: Invalid ticket number". I am not following development closely, but I see no report of any incident on wp-meta, and have not been notified of any.

That issue is now tracked in ticket #8195.

I am leaving priority to normal as there have been 10 new reports since the once which vanished, and I verified that all remain so far. I also went back over the tickets created over the previous year and could not find any other loss. This could be caused by a database rollback between 2026-03-02T01:03:04Z and 2026-03-04T04:58:29Z, but my WordPress profile shows that profiles.wordpress.org suffered no such incident.


P.S. In order to create this ticket, I had to check the “I am not reporting a security issue” field.

This report (including all messages and attachments I add to it) is offered under the terms of CC0 1.0.

Change History (2)

#1 follow-up: @dd32
5 weeks ago

  • Resolution set to invalid
  • Status changed from new to closed

I'm guessing it was deleted, as you appear to be reporting an issue in the upstream Trac project.

I've just closed your new ticket as invalid as such.

When someone deletes a ticket because someone is lost, they're supposed to comment and @chealer mention you so that you get a notification as to why.. I guess they considered it to be spam, rather than just lost.

#2 in reply to: ↑ 1 @chealer
5 weeks ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

Replying to dd32:

I'm guessing it was deleted, as you appear to be reporting an issue in the upstream Trac project.

I've just closed your new ticket as invalid as such.

I fixed it; as you would have seen had you read that ticket, if that originates from an issue in Trac, there is already a ticket upstream.

When someone deletes a ticket because someone is lost, they're supposed to comment and @chealer mention you so that you get a notification as to why.. I guess they considered it to be spam, rather than just lost.

Triagers would not delete a ticket unless it was badly lost.

It would also be inappropriate for a triager to delete a ticket as spam while leaving the account intact and failing to look at other tickets and comments.

Thanks for the hypotheses, but in any case, if deletion was the explanation, logs would say.

Note: See TracTickets for help on using tickets.