WordPress.org

Making WordPress.org

Opened 3 years ago

Last modified 5 months ago

#2192 new defect

Change the name of "invalid" ticket resolution

Reported by: pento Owned by:
Milestone: Priority: normal
Component: Trac Keywords:
Cc:

Description

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.

Change History (3)

#1 @SergeyBiryukov
3 years ago

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.

Last edited 3 years ago by SergeyBiryukov (previous) (diff)

#2 @pento
5 months ago

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.

#3 @dd32
5 months ago

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.

Note: See TracTickets for help on using tickets.