Update: More up to date information was detailed in a more recent post, Reverting the Bulk Ticket Closing.
On January 4, there was a bulk ticket Created for both bug reports and feature development on the bug tracker. edit in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. that affected approximately 2,300 tickets spanning all components that had not been modified in at least 2 years. The bulk action performed was setting the ticket status to closed with a resolution of
A full list of the tickets closed can be viewed using this Trac query.
Follow Up Discussion
During last week’s devchat, there was a productive discussion about what happened and how to move forward from there. Listed below are some of the main takeaways:
- The bulk edit was not related to the recent Short Term Trac Milestone Ticket Triage Proposal.
- A goal of the new Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Team will be to establish better processes for performing updates to tickets, including bulk updates if any are warranted.
- Bulk actions spanning multiple components should be communicated ahead of time.
- Each component having hundreds of open tickets makes it difficult for new contributors to see where they can help most.
- Many tickets take a lot of institutional knowledge to identify the best paths forward.
- Component maintainers and Trac gardeners need clear expectations for how to treat those closed tickets. Triaging tickets that are closed is hard.
wontfix keyword may not have been appropriate here. “Won’t fix” sounds like an active decision based on the lack of merit for a ticket. This may not be the case for most of the tickets closed.
- Perhaps older tickets are getting lost in the reports currently offered on Trac.
- Suggested Solutions
wontfix needs to be re-evaluated.
maybelater is a resolution that fits this scenario better.
- Define or agree on what constitutes “no activity”
- A “stale” designation may help. Stale notices could remain open but be hidden from standard reports.
Proposed Path Forward
After the conversation in devchat, it was decided that this post would be a better place to continue discussion and reach a final conclusion.
Below is the process moving forward that is being proposed after taking into account all of the feedback received so far:
- All tickets closed in the bulk edit due to inactivity will have their resolution changed from
- Component maintainers are free to reopen tickets closed as a result of this bulk action, as long as they have a plan to triage the list within a reasonable amount of time.
- Just like component maintainers are free to reopen the tickets closed, they are also free to leave them closed. But, the closed tickets should be scrubbed to make sure that no important tickets were closed accidentally.
Those in the component maintainer role would discuss these options in their component meetings or Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. rooms and reach a decision of what path works best for them.
The actions chosen for each component should be communicated in the component’s weekly meeting summary and in the comments below. The plan should also be clearly communicated in the form of a comment in Trac if the tickets are reopened.
If a component wants to reopen their tickets but needs help scrubbing the list, include that in your comment below and a plan can be created for going through the list. The three components without active maintainers (Filesystem API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., Pings/Trackbacks, Rewrite Rules) will have the closed tickets scrubbed by myself (@desrosj) and other members of the Triage Team (once it is fully formed) to ensure nothing important was closed.
The correct way to reopen tickets for the components that wish to do so will be communicated once it is determined. The best way forward will depend on the feedback on this post and from component maintainers. But, this could be one of the following:
- Bulk edit to reopen component by component.
- Trac database query to reopen, remove resolution, comment.
Below is a summary of the number of closed tickets grouped by component:
- Administration: 118
- Autosave: 7
- Bootstrap/Load: 18
- Build/Test Tools: 27
- Bundled Theme: 10
- Cache API: 16
- Canonical: 30
- Charset: 6
- Comments: 63
- Cron API: 11
- Customize: 49
- Database: 34
- Date/Time: 11
- Editor: 76
- Embeds: 12
- Emoji: 2
- Export: 24
- External Libraries: 13
- Feeds: 17
- Filesystem API: 24
- Formatting: 100
- Gallery: 16
- General: 172
- HTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. API: 17
- Help/About: 6
- I18N Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: 28
- Import: 36
- Login and Registration: 54
- Mail: 18
- Media: 163
- Menus: 77
- Networks and Sites: 40
- Options, Meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. APIs: 40
- Permalinks: 53
- Pings/Trackbacks: 15
- Plugins: 53
- Post Formats: 4
- Post Thumbnails: 4
- Posts, Post Types: 151
- Query: 69
- Quick/Bulk Edit: 24
- REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.: 5
- Revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.: 13
- Rewrite Rules: 37
- Role/Capability: 17
- Script Loader: 25
- Security: 14
- Shortcodes: 18
- Taxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.: 73
- Text Changes: 13
- Themes: 73
- TineMCE: 56
- Toolbar: 12
- Upgrade/Install: 80
- Upload: 25
- Users: 102
- Widgets: 59
- WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Site: 3
- XML-RPC: 27
Do you have more to add to the discussion? Concerns with the proposed plan above? Please share them below!