Change the name of "invalid" ticket resolution

[pento]

Particularly for Trac newbies, "invalid" can feel like a bit of a put-down, even with an explanation of why the ticket is being closed.

Maybe not-a-bug, not-a-core-bug, or something of that nature would be better?

Bikeshedding welcome on this ticket.

[SergeyBiryukov]

not-a-core-bug seems good to me. It would be helpful for things like ​#WP37367, ​#WP37864, or ​#WP38428, where the report is technically valid, it's just not a core issue.

However, if the new resolution contains dashes, others should be updated to use dashes too for consistency: wont-fix, works-for-me, maybe-later.

[pento]

After the mass closing of core.trac tickets a few weeks ago, there's been some discussion on more appropriate ticket resolutions.

​https://make.wordpress.org/core/2019/01/14/follow-up-on-recent-trac-bulk-edit/

Adding a stale resolution would be helpful, to show tickets that can be re-opened as soon as someone wants to work on them.

I'm not exactly sure how trac workflows are configured, but I think it'd be appropriate to automatically change the Milestone to Awaiting Review if a stale ticket is reopened.

[dd32]

I'm not exactly sure how trac workflows are configured, but I think it'd be appropriate to automatically change the Milestone to Awaiting Review if a stale ticket is reopened.

For that, I think we'd need to use ​AdvancedTicketWorkflowPlugin's reset_milestone feature instead of our current ConfigurableTicketWorkflow.

[SergeyBiryukov]

A proposal for this was published a while ago:
​https://make.wordpress.org/core/2020/06/24/proposal-rename-invalid-worksforme-and-wontfix-ticket-resolutions/

Next steps would be to summarize the various suggestions in the comments, and reach a conclusion.

[dd32]

Just waiting on the final line up of stati, and we'll change it over for core, meta, buddypress, and bbpress (They're all interlinked).

[dd32]

Still waiting on